It gets altered and certain features stripped out before we get it. The CK we use isn't the same as the one Bethesda uses. The very fact that Skyrim.esm unexpectedly changed size is your clue that it isn't like the others and you are headed down a bad path.
#How to use tes5edit to esm mod#
We don't mod Skyrim.esm because we don't have any tools that can do so safely and because it's bad development practice that would ultimately lead to far more problems that it would solve. The special things they do add (for example, Dawnguard adding Vampire Lord and Werewolf Perk Trees) seem to actually be tied to the Engine somehow- even if you don't have Dawnguard.esm in your Data fold, you can still view the (empty) Vampire Skill Tree, which you cannot do for any non Skill-tree Actor Values. esm/.esp presumably there is some hard-coded links within the engine itself to Skyrim.esm to make certain things work (for example, somehow Skyrim.esm can contain Perk Trees/Skills, but we cannot make them-even if we duplicate and edit them, the best we get is nothing most likely the Engine directly references those Forms somehow.) There are like a dozen-or-so Forms hardcoded, but everything else comes from a. BV scripts might still presume that records are as meant, which can cause issues in the effectively 'is' the game-go move it somewhere, and try to load up the main menu: it CTDs after the splash screen. However, second mod may port vanilla records that overwrite changes made by Better Vampires, which prevents BV from working correctly.Ĭonflict like that would be a direct compatibility issue, where last mod would be incompatible with BV and first mod without a patch. LOOT sorts second mod below both, because it changes records from first mod in between. If other mod is conflicting Better Vampires in a radical way, then that is likely to cause issues.įor example: you have Better Vampires. If you have issue related to Better Vampires, then you can see the records in 圎dit to check which files are conflicting with it. However, they become very clear with few looks, when you think what mod is actually supposed to do.īetter Vampires edit Vampires in Skyrim, so it will naturally conflict with base game and DLC records. It may be hard to determine which conflict is relevant at first. Mod right in the view will win conflicts in records against files in left - in that order. XEdit shows record conflicts in similar way. For example: USLEEP is below official DLCs, because it is meant to win record conflicts against them. This is exactly what load order is for: mod lower in the load order has higher priority. Game works so that records loaded last will win the conflicts.
These colors do not always indicate a problem, but point out how many files are editing record.
#How to use tes5edit to esm Patch#
USEEP naturally edits all of them, being a patch for them.Ĭonflicts are marked with colors. For example, official DLCs edit records from previous files, because they add to game, to Update.esm and sometimes in to each others as well. You will always have conflicts in your game. It is important to note that conflicts are not bad.
0 kommentar(er)
