Jump to content

[LE] ;CODE NOT LOADED issue in Creation Kit?


samv96UK

Recommended Posts

Found the decompiler here. No idea if it works, but maybe worth a try.

 

Thanks for looking, but it's probably too late. I've just deleted all of the scripts and I'm going to start from scratch. I'll remember to back them up along with my .esp's in future though.

Link to comment
Share on other sites

I have this same problem and it occurred right around the time of the Skyrim 1.7 update and the Dawnguard installation. I suspected those things. It sort of looked like Bethesda destroyed modding and nobody would be able to build or edit mods with scripts anymore. So it would be nice if this is not the case and it is just my computer and there is a way to fix it.
Link to comment
Share on other sites

I have this same problem and it occurred right around the time of the Skyrim 1.7 update and the Dawnguard installation. I suspected those things. It sort of looked like Bethesda destroyed modding and nobody would be able to build or edit mods with scripts anymore. So it would be nice if this is not the case and it is just my computer and there is a way to fix it.

 

Actually, I never thought about that. I hadn't edited the scripts since I installed Dawnguard on Sunday, and they were fine before that. I think it's just where the scripts may have been moved or changed somehow because of the DLC. I've managed to save a new script I've done today, so I'm not sure whether it is okay now or not.

Link to comment
Share on other sites

I think this issue is unrelated to Skyrim or the CK itself.

 

Could be more a conflict with our OS, since the files getting deleted are simply "stuff in a folder". What i think is that sometimes our pc loads a precedent configuration, where those files weren't created yet. What i don't understand is why for example the PEX versions are still there.

 

Happened to me that 2-3 modding sessions were gone, so the esp looked like 1 week before.

 

About the quest not working, i think i can say that is unrelated to this. Think about the actual Dawnguard and Skyrim before the CK release. There weren't any source scripts, just the PEX in the BSAs.

 

Stuff to work just needs the compiled script, the source only serves to allow editing.

 

So your quest not starting could be related to the bug someone encountered after the 1.7/Dawnguard release, wich almost everyone fixed by making a save with the ESP loaded and retrying (and someone else by saving the ESP with the new update). It doesn't really matter actually, since not being able to edit my quest leads me to redo it anyway.

Link to comment
Share on other sites

I think this issue is unrelated to Skyrim or the CK itself.

 

Could be more a conflict with our OS, since the files getting deleted are simply "stuff in a folder". What i think is that sometimes our pc loads a precedent configuration, where those files weren't created yet. What i don't understand is why for example the PEX versions are still there.

 

Happened to me that 2-3 modding sessions were gone, so the esp looked like 1 week before.

 

About the quest not working, i think i can say that is unrelated to this. Think about the actual Dawnguard and Skyrim before the CK release. There weren't any source scripts, just the PEX in the BSAs.

 

Stuff to work just needs the compiled script, the source only serves to allow editing.

 

So your quest not starting could be related to the bug someone encountered after the 1.7/Dawnguard release, wich almost everyone fixed by making a save with the ESP loaded and retrying (and someone else by saving the ESP with the new update). It doesn't really matter actually, since not being able to edit my quest leads me to redo it anyway.

 

I've decided I'm just going to leave the scripts 'till I've completed EVERYTHING else in the mod. That way I'll be able to get them all done in 2-3 days at the end of the project.

Link to comment
Share on other sites

I've seen this issue before Dawnguard and I found this is usually because your trying to open a script that is in a .bsa file. The Creation Kit cannot open other .bsa files directly and can only access Skyrim's base .bsa files, unless you add them in the SkyrimEditor.ini under:

 

 

[Archive]

 

SResourceArchiveList2=Skyrim - Shaders.bsa, Update.bsa, (yourbsafile).bsa

If your scripts are not in a .bsa file then you might have a corrupt file, I recommend you try opening your scripts in a program like Notepad++ and write the code in that way.

Link to comment
Share on other sites

Beth doesn't pack source script in their BSAs.

 

If you unpack their script folder you'll only see the compiled version (PEX) of the scripts.

 

And the PEX script is necessary for the game to use it. To see the fragment/edit the script in the CK you need the PSC script.

 

The Skyrim sources became available with the CK release, prior to that there wasn't the script folder (because PEX are already in the BSA).

 

So the scripts he is seeing with that error miss PSC. If they are vanilla, then verifying the CK cache via Steam will solve. If they are custom, they are gone.

Link to comment
Share on other sites

  • 1 year later...

Nice necro...

 

At any rate...

DLC source scripts have to be moved out of their respective subfolder and placed in the main source folder before the Creation Kit will recognize them.

Mod source scripts need to be extracted from their respective BSAs and placed in the main source folder.

In some cases (some of my mods) the source scripts need to be moved from a mod subdirectory in the source folder to the main source folder.

Link to comment
Share on other sites

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...