Plan your playthrough and find the mods to cater to your idea of the world. If there is not enough info on the page for mod placement, ask yourself why you're downloading the mod.ĭoes it just have a nice title? Does it claim to be immersive and so you think you need it? Are you going by the star rating alone? Don't.
Once you're comfortable with the section definition, read your mod description page. You need to understand how the game loads mod data and how to place those mods in the right order. The second tab explains the section definitions so you can better place your mods. The first tab is all the technical information about how to download mods, how to remove them, Once you've downloaded your LLO you will find several tabs at the bottom (scroll down it). By codifying what's being doneīehind the scenes, you are armed with more knowledge at your fingertips. I have simplified the understanding of different areas of the game we're allowed to edit inside the Creation Kit. Whichever mod is lower will have the edit to the bush loaded into your game.
The lowest mod wins the conflict in the load order.Įxample: Mod A moves a bush in Dawnstar and mod B also moves that bush. You can have a "conflict" by which it is resolved depending on where a mod is placed and it will cause no crashing. The first step is to understand that Conflict is not the same as Crashing. There are no ifs and ands or buts about it- we Mod Author's (MA's) and Original Mod Authors (OMA’s) must clean our mods! These are mods that have been improperly imported from 32bit to 64bit and weren’t cleaned in 圎dit.Įven mods made in 64bit need to be cleaned! Changes from the Unofficial Skyrim Special Edition Patch (USSEP) should always carry over even if USSEP isn’t a requirement. 9 times out 10 your crash is being caused by a “dirty” mod.
0 kommentar(er)
