Download the premade CreationKitCustom.ini here.There are a few edits that need to be made before you can use the CK to port mods. Select "Yes" in the "Script Source Extraction" box.After completion of the installation, click on "Play".Select "Creation Kit: Skyrim" and select "Install".In the left pane, expand options to show "All Games" via >.Run the Launcher and sign in (create an account if you don't have one).
While you won’t be building new mods in this guide, you will be importing mods originally designed for Skyrim LE, and the Creation Kit will allow you to re-save (and thus, update) them to work with Skyrim SE. ini, and the “default” configuration generates when the tool runs for the first time. Much like with Skyrim itself, the Creation Kit doesn’t ship with a pre-configured. It has been available in one form or another through the release of the last several Fallout and Elder Scrolls games and is invaluable if you have any interest in working with mods for modern Bethesda games.īeyond allowing users to build their own completely original mods, the Creation Kit (or CK) can tweak and change things throughout both mods and official content in ways not possible through other tools. The Creation Kit is the official Bethesda tool for creating and editing mods.
Rather than detail this procedure, we recommend reading this article for details on how to do so. In the event that it still updates, it is possible to roll back to an earlier version.
Since we will be launching Skyrim via MO2 and the SKSE launcher, no trigger event will occur and your Skyrim install will remain in the same state as it currently is until you force the update yourself.
Files downloaded from the "Main Files" section should be installed as separate mods in MO2.These individual downloads should be handled according to the following guidelines unless otherwise specified:
Many mods contain multiple parts or several downloads. Please, for Talos' sake, read the Nexus description of every mod you install. You should expect these errors, at least until I tell you to run LOOT, as they are due to how drastically this guide changes the game. If you choose to disregard this warning, you will see many errors in LOOT. If you are not willing to teach yourself how to use all of the modding tools used in this guide.If you do not carefully read and follow every word of the guide.If you add or remove other mods before completing the guide.Your game MAY APPEAR BROKEN, and LOOT will not sort correctly: I'm fairly confident this is an issue obviously despite the fact it looks like it's trying to save a backup, but I'm not sure what to look for in my data folder.Before we get started, we need to have a quick but essential chat. Please check the files in your data path: "D:\Steam\steamapps\common\Skyrim Special Edition\Data\" One or more errors occurred during renaming of saved modules. Then I try to close the program and I get a couple of errors.Ĭould not rename "D:\Steam\steamapps\common\Skyrim Special Edition\Data\Update.esm" to "D:\Steam\steamapps\common\Skyrim Special Edition\Data\SSEEdit Backups\.2019_08_15_10_15_00".Ĭould not rename "D:\Steam\steamapps\common\Skyrim Special Edition\Data\Update.esm" to "D:\Steam\steamapps\common\Skyrim Special Edition\Data\SSEEdit Backups\.2019_08_15_10_20_53". When I run the quick auto clean executable on the update.esm, it runs and the final two messages are Quick clean mode has finished and background loader has finished (or something like that).