All tools have to be launched directly from MO, and this is why you point it to the executable rather than the folder. This same method applies to any that you add, but you may find it adds some automatically. having Beth's stuff on the same drive as Windows isn't the best as the UAC interfears with the game,that aside you could look at these lines in the Creation kit ini file bAllowMultipleMasterFiles1 SResourceArchiveList2Skyrim - Shaders.bsa, Update.bsa, Hearthfire.bsa, Dawnguard.bsa, Dragonborn.

If you already have the Launcher running when you redeem this code you must close it and reopen it for the the SSE CK to appear. Find the CreationKit.exe, click on it, and then click open. Once it is installed it can be launched through the CreationKit.exe without needing the BethNet launcher. If not, follow these instructions - click on the tab with three dots opposite Binary and navigate to the main Skyrim folder. MO: Creation Kit should be added automatically by MO2 to the executables.

Simply download the main file, and copy/paste CreationKitCustom.ini into your Skyrim Special Edition folder (the same place where you have Creation Kit installed). There's an issue with the Creation Kit in that you can't load more than one master, but this can be easily fixed with this - Creation Kit Custom (Main Files). To install the CK, search for Skyrim Special Edition: Creation Kit on Steam and download it.įollow the steps and it should suggest to install the Creation Kit into your Skyrim Special Edition folder, which is where you want it to be.

Bethesda creation kit launching issues