Woodwose Posted February 6, 2021 Share Posted February 6, 2021 (edited) Hello,i did some Modding with previous Fallout-Games years ago and it worked quite well. Now startet skyrim-SE and just wanted to do some minor changes with the creation kit, but here i completely failed somehow. At start everything worked fine. The few mods i downloaded and installed, do what they should, no crashes occured. But hen i tried to do my personal version of ineed-continued. All i did was changing some stats of some items of the already existing and working mod. But these items all end in a CTD. In the end i just edited the name of one single item (yes, the name, not the ID or anything). I just loaded the ineed.esp, selected the item, typed in the new name, klicked ok and saved the mod. In the game, the item shows up with the new name, i can pick it up, but when i try to look at it in the inventory, the next thing i see is my desktop. No matter if i create a new plugin or change the existing mod. I know there are a lot of issues with a "ctd when opening inventory bug" and i looked up a lot of solutions, but nothing there is related to my situation. Without my changes i have no problem with crashes. How can such a minor change create such an issue?? I'm just editing one line of pure text! I'm really confused. My only explanation is, i'm doing some stupid error, but i can't figure it out.Edit: Before anyone asks: Yes, i have the new version of creation kit, the one you have to download from bethesda.By the way: Sorry for the typo in the title! Edited February 6, 2021 by Woodwose Link to comment Share on other sites More sharing options...
IsharaMeradin Posted February 7, 2021 Share Posted February 7, 2021 Did you create a new plugin with INeed.esp as a parent master?Or did you edit the INeed.esp directly? If you attempted to make a patch file for INeed, it sounds like INeed wasn't properly designated as a parent master. The fix for this is to change the internal header flag that indicates the plugin is an ESM, ESP or ESL. The CK needs to think that it is an ESM otherwise it won't properly assign an ESP as a parent master and any edits will create duplicates. And such duplicates may not contain all the necessary data to work correctly, thus potentially causing CTD. But you're in luck, instead of needing to mess with SSEEdit or Wrye Bash to change that flag, you can install SSE Creation Kit Fixes which incorporates a "fix" to allow the CK to use ESP files as plugin parents without any need to edit. Link to comment Share on other sites More sharing options...
Woodwose Posted February 7, 2021 Author Share Posted February 7, 2021 (edited) Did you create a new plugin with INeed.esp as a parent master?Or did you edit the INeed.esp directly?Both with the same result. But .. If you attempted to make a patch file for INeed, it sounds like INeed wasn't properly designated as a parent master... that might still be the problem. Actually i edited the "ineed-extended.esp" which uses the "core"-ineed.esp as a master. i'll try out your suggestion. Edit: Problem solved! This fix did it. Thanx for the help! Edited February 7, 2021 by Woodwose Link to comment Share on other sites More sharing options...
Recommended Posts