payl0ad Posted February 18, 2018 Share Posted February 18, 2018 (edited) Hey everybody, I recently had to reset my Creation Kit ini files because it stopped drawing lights. Afterwards, when I try to add a property to a Papyrus Fragment on a Terminal, the CK does nothing except throw an error message in the warnings window: SCRIPTS: Cannot open store for class "Fragments:Terminals:TERM__031229D5", missing file? I already re-unpacked all the sources zips but it didn't help. The file is indeed missing, but how am I supposed to have that file before creating it? I obviously can't compile because the compiler throws the same error. Anybody know how to fix this? I'm working on an update for a mod but I can't proceed until this is fixed. Here's my CreationKitPrefs.ini and CreationKitCustom.ini. Edited February 18, 2018 by payl0ad Link to comment Share on other sites More sharing options...
JonathanOstrus Posted February 18, 2018 Share Posted February 18, 2018 (edited) Are you editing a vanilla terminal? That doesn't appear to belong to any Bethesda DLC that I could find via the form ID ref. What esm/esl/esp files are you loading? It could likely belong to a 3rd party plugin. Edited February 18, 2018 by BigAndFlabby Link to comment Share on other sites More sharing options...
payl0ad Posted February 19, 2018 Author Share Posted February 19, 2018 I'm working on a copy of some DefaultTerminal in an ESP file that I created, which has DLCFarHarbor.esm, DLCNukaWorld.esm and Fallout4.esm as masters. I did this very same thing before (long before the ini reset) and it worked, right now I'm working on it because on this specific terminal, my original fragments wouldn't run. I have the same (code-wise) fragment attached to another Terminal, which works fine. I also get the same issue on a completely blank new copy of any DefaultTerminal. The ID in the error message is the RefID of the placed Terminal object. Link to comment Share on other sites More sharing options...
JonathanOstrus Posted February 19, 2018 Share Posted February 19, 2018 Ok based on you only loading 3 masters, FO4, FH, and NW. Then the plugin you're creating is the load index 03. Which it's saying it can't find the script to go with the terminal in your plugin not any dlcs. Fragments can be wonky at times. The best solution I have for you is to use the object window to dupe it (don't open and change name then try to save to generate the copy). That way the form ID and all is set ready to go. Then open the new terminal you want to edit. Go down to wherever and just put in a comment ; for the fragment. Hit ok to save and close the terminal. Then go back in and you should be able to edit the properties. I always do that because things get weird and don't always work right. But that seems to work each time. Link to comment Share on other sites More sharing options...
payl0ad Posted February 20, 2018 Author Share Posted February 20, 2018 OK, I tried with a new copy of a DefaultTerminal (the one I was using was also copied from that though) and it worked the way you described. Guess I don't want to find out why exactly the old one stopped working for no good reason... thanks for your time! Link to comment Share on other sites More sharing options...
Recommended Posts