Jump to content
  • 0
Naoko

Mods *not* to clean with TES5Edit

Question

So, after reading/watching tutorials for TES5Edit and using it to clean my main .esm files, I got the impression that I should use it to clean pretty much everything except skyrim.esm, the unofficial patches and a very small number of mods that contain intentional dirty edits.

 

I'm wondering if there's a comprehensive list of things I should definitely NOT clean (in order to avoid breaking them or creating conflicts where there would be none, etc.), or if that list is so small that it shouldn't be a problem?

 

I've read through several places/guides already, like here https://www.creationkit.com/TES5Edit_Cleaning_Guide_-_TES5Edit#Quick_List_of_What_Not_to_Clean

 

and here https://www.creationkit.com/Skyrim_Dirty_Plugins_List#Mods_You_Should_NOT_Clean

 

but the number of things really does seem quite small.

 

Also - I understand that it's usually very important to clean mods in order to avoid conflicts and potential in-game wonkiness/CTDs, but although I just started attempting to mod Skyrim for basic stability/bug-fixes, I did end up with a bunch of stuff in my Mod Organizer folder that I'm not sure should be cleaned or not. There's an SKSE-Scripts mod, as well as PapyrusUtil, Distant Decal Fix and Stable uGridsToLoad in MO so far, and I don't know if they require cleaning. *the mods in the screenshot haven't really been organized yet, as I'm still in the process of installing new ones and figuring out what to clean or not.

 

Apologies if this was explained elsewhere and I missed it >_< I just want to make sure I don't break something on my first attempt, before continuing. :)

post-7524-0-29816900-1438371203_thumb.png

Edited by Naoko

Share this post


Link to post
Share on other sites

Recommended Posts

  • 0

LOOT tells you what to clean. Also, only mods that have plugins are cleanable. Everything else can't be cleaned.

Share this post


Link to post
Share on other sites
  • 0

Hey,

 

I am not sure wheter I am at the right topic, or not. :/ But found this one suitable.

 

I have some mods with cleanable ITMs, but I am not sure should I clean them, or shouldn't. Tried to ask mod authors, but lots of topic are inactive or mod authors also didn't know the exact answer. (Just, to be safe and make backup, etc...)

 

These mods are:

 

1.) The Oblivion Realms Serie - Morthal Pain

ORS_MorthalPain.esm

 

[Removing "Identical to Master" records done]  Processed Records: 13367, Removed Records: 8

 

2.) Relighting Skyrim-No JIT (Legendary) Ext. + Int.

RelightingSkyrim_Legendary.esp

 

[Removing "Identical to Master" records done]  Processed Records: 17182, Removed Records: 4

 

3.) Helgen Reborn

Helgen Reborn.esp

 

[Removing "Identical to Master" records done]  Processed Records: 27251, Removed Records: 7

 

4.) Custom Family Home (Optional Additional Familiy Room)

Custom Family Home.esp

 

[Removing "Identical to Master" records done]  Processed Records: 162, Removed Records: 8

 

These are which ones LOOT does not sign as "faulty" plugins, but they have ITMs.

Other mods, which were signed by LOOT I have cleaned.

 

I need some infos.

 

Thank you!

 

Ps: "The automated cleaning function "Remove Identical To Masters records" take care of everything and is safe to use."

 

I've read that one. :)

 

For instance:

 

Hunterborn also has ITMs, but according to the mod author do not clean those ITM records, because they a quest line.

 

Do not clean them. ITM's are not always dirty.
Cleaning them will break the Strange Claw questline.

Edited by kranazoli

Share this post


Link to post
Share on other sites
  • 0

Intentional ITM records work only for mods that load after the conflicting ones, not before, and even then it will interfere with them by having that forced identical records. Any so called "intentional" ITM records should be cleaned anyway and conflicts must be resolved with a proper load order, a compatibiity patch, or not using conflicting mods at all if nothing else works. ITMs won't cure conflicts and make mods play nice together if they conflict on critical data no matter how many ITM records a mod author is trying to leave in his/her plugin to preserve vanilla records.

  • Upvote 2

Share this post


Link to post
Share on other sites
  • 0

Okay, you are zilav and I am who I am.

I am sure you can solve any kind of issue with your knowledge, but I am just a player. Two mod authors said that, no three of them they have no idea what will happen if I clean they mods. They said, they are working fine with those ITMs records, as well. But as you read the mod author of Hunterborn mod said do not clean Hunterborn.

 

If I am not mistaken there are others: Guard Dialog Overhaul, and one more... Honestly I do not really understand why I can't make for instance some kind of white list via LOOT. Mods I do not want to clean, but I do not want to se the annoying warning always.

 

I am sure this conflict could be solveable by a proper patch if anything has gone wrong way, but I am still hesitate what would be the good choice.

 

I know, if I clean for instance Hunterborn and it is true that cleaning that mod break the mentioned quest line, I don't have the knowledge to solve that issue, and mod authors mostly retired. They are passive, etc...

 

Ps:

 

Helgen Reborn which is also has ITM records:

 

"Not necessary because it's been cleaned record by record. The first set are not errors but simply warmings and are showing up because of how the aliases work in those packages. The so called ITM's are in a completely custom worldspace and it's beyond me how a custom worldspace can show ITM records."

 

I have fixed these issues:

 

[00:00] Checking for Errors in [02] Helgen Reborn.esp
[00:04] BalokGuardsRadiant05ToKorst [PACK:020DEC04]
[00:04] PACK \ Package Data \ Data Input Values \ Value \ PLDT - Location \ Location Value -> <Warning: Quest Alias not found in "BalokRadiant05 "Changing of the Guard" [QUST:02023591]">
[00:04] BalokGuardsRadiant04ToKorst [PACK:020DEC03]
[00:04] PACK \ Package Data \ Data Input Values \ Value \ PLDT - Location \ Location Value -> <Warning: Quest Alias not found in "BalokRadiant04 "Changing of the Guard" [QUST:02023590]">
[00:04] BalokGuardsHerdRadiant03ToKorst [PACK:020DEC02]
[00:04] PACK \ Package Data \ Data Input Values \ Value \ PLDT - Location \ Location Value -> <Warning: Quest Alias not found in "BalokRadiant03 "Changing of the Guard" [QUST:0202358F]">
[00:04] BalokGuardJotoRadiant02ToKorst [PACK:020DEC01]
[00:04] PACK \ Package Data \ Data Input Values \ Value \ PLDT - Location \ Location Value -> <Warning: Quest Alias not found in "BalokRadiant02 "Changing of the Guard" [QUST:0202358E]">
[00:04] All Done!

 

But still left these:

    
[Filtering done]  Processed Records: 917126 Elapsed Time: 00:05
Removing: GRUP Cell Temporary Children of [CELL:02110326] (in aaaWereBalokDungeonWorld "Staadomaar Temple" [WRLD:021102F4] at -3,-1)
Removing: GRUP Cell Temporary Children of [CELL:02110324] (in aaaWereBalokDungeonWorld "Staadomaar Temple" [WRLD:021102F4] at -6,-1)
Removing: GRUP Cell Temporary Children of [CELL:021102FB] (in aaaWereBalokDungeonWorld "Staadomaar Temple" [WRLD:021102F4] at -5,-1)
Removing: GRUP Cell Temporary Children of [CELL:021102F9] (in aaaWereBalokDungeonWorld "Staadomaar Temple" [WRLD:021102F4] at -4,-1)
Removing: GRUP Cell Temporary Children of [CELL:0211031C] (in aaaWereBalokDungeonWorld "Staadomaar Temple" [WRLD:021102F4] at 49,-10)
Removing: GRUP Cell Temporary Children of [CELL:0211031B] (in aaaWereBalokDungeonWorld "Staadomaar Temple" [WRLD:021102F4] at 3,-2)
Removing: GRUP Cell Temporary Children of [CELL:0211031A] (in aaaWereBalokDungeonWorld "Staadomaar Temple" [WRLD:021102F4] at 2,-2)
[Removing "Identical to Master" records done]  Processed Records: 27251, Removed Records: 7, Elapsed Time: 00:00

 

And Mike Hancho a very helpful author. But nothing more advice just keep backup if I clean those ITMs records.

Edited by kranazoli

Share this post


Link to post
Share on other sites
  • 0

Injected records can show up as ITMs.  Cleaning these won't always cause issues, particularly if you are following good practice and make no changes to your load order once you have cleaned the mods.  However, removing those records from their files, or any other files built to be compatible with them, could create trouble if you then add or remove files from your load order, or create a new profile using some of the same plugins.  If you do everything correctly, making sure to load and clean each mod one at a time, then I still don't think you'll have any problems, but there is no reason to remove those records, and it's much safer to leave them there.  That is why I recommend that people do not clean my mods.  Guard Dialogue Overhaul also uses injected records, so the warning to not clean that mod may be for the same reason (I haven't looked into this personally, so I'm not certain about GDO's reasons).

 

I think the general statement that using "Remove Identical To Masters records" is safe in every situation and for every mod, even against the recommendations of the mod author, is a dangerous thing to say.  No mod user should be blindly cleaning mods without any thought or consideration for the records they are removing.  As someone who has had to deal with the repercussions of people mis-cleaning my mods, I find this assumption and advice really aggravating.

Share this post


Link to post
Share on other sites
  • 0

What Krypt just said. As a general rule, I only clean files called out for it by LOOT. There is a mod in the STEP lineup, as mentioned earlier (GDO) where the ITMs are, indeed, intentional and required for proper operation. So yeah... just go with the LOOT advice, unless it breaks the load, then revert. :)

Share this post


Link to post
Share on other sites
  • 0

Ok! Thank you all of your support. I have cleaned every mods which required by LOOT.

Only two exceptions:

 

- Hunterborn

 

I also wrote at the mod topic, why do not sign towards LOOT Team that handle Hunterborn like GDO, because if it's still true that harmful to clean it, lots of fellows will clean because LOOT said that.

 

- Remove Interior Fog V2 - Full Version.esp

  Remove Interior Fog V2 - Full Version.esp
  Contains 3 ITM records. Clean with TES5Edit.  

 

I just can't able to clean it. It looks clean, but LOOT says it should be clean.

 

Ps.:

 

Don't you guys know, why can't we add a mod as a custom exception or whitelist via LOOT. Which is okay dirty, understood but please do not bother me the annoying cleaning that mod warnings?

Share this post


Link to post
Share on other sites
  • 0

What is an injected record?

Record with modified formID so it begin with 01 instead of the plugin's index. It allow multiple mods to share the same record as if it was in Update.esm, thus enabling them to work within some kind of framework (both plugins can reference the same injected record without having a common master).

 

(I really need to go back to finishing this xEdit guide...)

 

 

As for GDO : Yeah, you should definitely not clean it, as their is nothing to clean anyway. The LOOT warning is an artifact from older versions where GDO was relying on SPIKE.esm

Edited by Kesta

Share this post


Link to post
Share on other sites
  • 0

Okay, after that discussion, how what is your opinion about Hunterborn?

 

https://www.nexusmods.com/skyrim/mods/33201/?tab=4&&navtag=http%3A%2F%2Fwww.nexusmods.com%2Fskyrim%2Fajax%2Fcomments%2F%3Fmod_id%3D33201%26page%3D1%26sort%3DDESC%26pid%3D0%26thread_id%3D939546&pUp=1

 

1S6kWnH.jpg

 

unuroboros 78 kudos 1338 posts

 

"Do not clean them. ITM's are not always dirty.
Cleaning them will break the Strange Claw questline."

 

Thank you!

Share this post


Link to post
Share on other sites
  • 0

xEdit should not clean injected records having changed data, please provide test plugin to replicate this. Such bugs should be fixed if they are really present.

  • Upvote 1

Share this post


Link to post
Share on other sites
  • 0

Load any combination of WAF, CCO, SPO, CCF in Tes5Edit and clean any one of them.  I don't remember the last time I tested this, so perhaps it's changed in the last update, but I've been able to use "Remove Identical To Masters records" on any of these mods when they are loaded together to remove the injected records from all but one of them.

 

Most of the injected records shared by these mods are identical, so they show up as ITM records and are "cleaned" with this option.  They will still work as long as there exists one mod in your load order that is injecting the records they rely on.  However, if you remove that mod, or create a new profile using one of the cleaned files, or load the cleaned files into TES5Edit individually after having cleaned them this way, then you're going to run into issues By "cleaning" these files, you've actually created a set of broken files with the potential for missing records.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Similar Content

    • By sheson
      This is a beta of [FNV|FO3|FO4|FO4VR|TES5|SSE|TES5VR|ENDERAL|ENDERALSE]LODGen/Edit with terrain LOD meshes and textures generation.
      This is for experienced mod authors and users that know how to use xEdit, xLODGen or DynDOLOD already.
      Installation and Setup
      Download
      xLODGen beta 93 - based on 4.1.4b
      Unzip into a dedicated folder outside of any Steam, game or mod manager folders or special Windows folders like Program Files.
      Rename xLODGen.exe to [game mode]LODGen.exe (TES5LODGen.exe for example) or start with command line parameter -fnv, -fo3, -fo4, -fo4vr, -tes5, tes5vr, -sse, -enderal, -enderalse
      Use -o:"c:\OutputPath\" command line parameter to change where files are generated to, default is the game folder.
      Do not generate into any game or any mod manager folders.
      Requirements
      Microsoft Visual C++ Redistributable for Visual Studio 2015, 2017 and 2019 - Required by LODGen.exe/LODGenx64.exe and Texconv.exe/Texconvx64.exe. Get matching platform x86/x64 depending on which xLODGen.exe (x86) or xLODGenx64.exe (x64) is used.
      RTFM and Share Results
      See the included Skyrim-Occlusion-Readme.txt for a brief explanation of the Skyrim TVDT Occlusion data generation. Read the hints that are shown when the mouse pointer rests on a setting. Ask specific questions or give feedback in the dedicated Skyrim TVDT - Occlusion Data thread.
      See the included Terrain-LOD-Readme.txt for a brief explanation of the settings for terrain LOD generation. Read the hints that are shown when the mouse pointer rests on a setting. Ask specific questions about terrain LOD in this thread for a more in-depth explanation if required and share feedback (with screenshots) about results or problems.
      These tools generate LOD meshes and textures "exactly" like CK, but not like the meshes and textures which are shipping with the games (they are often manually edited).
      However, these tools provide more options and higher resolutions (use the x64 version if there are memory errors because you believe you require 4k or higher) and can be updated to add more useful features and options.
      I did some testing in the different games, but finding the best combinations of options and settings requires lots of testing and are a matter of personal opinion and which game is used, the load order, mods, even different worldspaces probably.
      That means, I am only able to give generic guidelines and hints to send you off to find and test for yourself and share your results. My main interested is that generations works correctly and without problems for now.
      Check out the thread xLODGen Terrain Settings Compare. Also refer to any modding guide which has a list of relevant mods close to your load order.
      The object and tree LOD generation is the same as the current versions of xEdit / xLODGen. Refer to their respective descriptions and explanations.
      Obviously, users of Skryim/Enderal/Skyrim SE/Skyrim VR/EnderalSE continue to use the easier and more comprehensive DynDOLOD for drastically improved object and tree LOD generation and only use xLODGen for terrain LOD (and maybe Occlusion) generation.
      First Time
      Here are suggestion to start without going crazy and that should be quick enough to generate:
      Set quality of meshes for LOD4 to 5 and then +5 for each next level. Or just set levels 8/16/32 to 10.
      Check protect cell borders (yes it fixes the ugly terrain drops at outer cell borders that still exist in Fallout 4).
      Use the max vertices setting only if you want to hard limit max file size.
      In Skyrim Special Edition or Skyrim VR, if you notice terrain briefly flickering when new areas are loading in, set [Display] bEnableLandFade=0 in Skyrim.INI
      Set Optimize Unseen to off for LOD4 for first generation. Start experimenting with a value of 550 with a quality setting of 10 or lower for LOD32 (used for map) and compare coastlines and file size to other settings.
      To quickly generate terrain LOD meshes just for the map, check only terrain LOD Meshes, check the Specific Chunk checkbox and set drop down to 32. Leave SW fields empty for complete map or set SW cell coordinates to same values as a *.btr filename to test a specific area with lots of water, river etc.
      Set texture sizes to 512 for a start. Larger sizes and large world spaces will take a considerable time (like 15 to 30 minutes or more easily). Each higher resolution means quadruple the work.
      Use DXT1 for diffuse and 565 (DXT1 if on Windows 7) for normal maps. If generating for Skyrim Special Edition use BC7. Uncheck mipmaps, raise steepness and Bake normal maps.
      For now, leave the Brightness, Contrast and Gamma at 0 and 1.0 respectively. It seems that only Skyrim CK and Skyrim SE CK are manipulating the intensity of the textures to adjust for the noise.dds and the god awful "improved" snow shader of Skyrim SE (just turn that thing off, really). If textures seem too dark in the game, brighten the noise.dds instead or vice versa. That way you can get perfectly matching LOD textures that look just like the textures in the loaded cells. For Skyrim a good average color of the noise texture seems to be around #C0. See below for a couple noise texture downloads.
      If you want to test larger texture sizes, use the chunk option to limit the number of textures that need to be generated. For example, check [x] Specific chunk, leave the drop down empty and set WS to the lower left cell coordinate of an 32x32 area, like 0, 0. It will then generate all textures up to 31,31. Not all worldspaces have their origin at 0,0 so you will have to check already generated meshes/texture filenames for their lower left coordinates.
      Questions and Feedback
      Obliviously anything related to terrain LOD should be posted in this thread.
      Posts related to Occlusion should be made here.
      Recommended Optionals
      TES5-Terrain-Tamriel.esm (Mega), SSE-Terrain-Tamriel.esm (Mega)
      TES5-Terrain-Tamriel-Extend.esm (Mega), SSE-Terrain-Tamriel-Extend.esm (Mega) - These extend the sea of ghost further to the north (see screenshots)
      SSE-Terrain-Tamriel-Full-Extend.esm (Mega) - Entire map from -96,-96 to 95,96 with northern ocean extension. Useful for mod authors.
      Put in game data folder obviously. Adds back terrain for Skyrim (Tamriel worldspace) at the outer edges so there is no missing terrain meshes/textures when generating terrain LOD for Skyrim.
      Load as early with lowest priority as possible, so that any other plugins overwriting or adding land records or cells with the same coordinates take precedence.
      Only required to be loaded when generating terrain LOD. No harm done when loaded in-game but typically the player can not get close to these areas. There are no effects outside the far away added cells.
      Noise
      Single color flat noise, Adjusted vanilla noise, HD Terrain Noise Texture SE
      Examples for Skyrim. Install to game folder like any other texture mod. The noise texture is applied in-game on top of terrain LOD textures, so no effect for LOD generation.
      Only the red channel is used in case the textures is not a grey channel format. MipMaps are ignored. The textures is tiled 3x3 per LOD quad, e.g. for LOD level 4, the noise texture is repeated 3 times to cover 4 cells, for LOD level 8, the noise texture is repeated 3 times to cover 8 cells and so on.
      Test-Terrain-Tamriel.7z
      For testing terrain LOD distances. Plain color terrain LOD textures for Tamriel with coordinates for every LOD quad. Green for LOD 4, yellow for LOD8, blue for LOD 16 and red for LOD 32.
    • By sheson
      DynDOLOD DLL for Skyrim, Skyrim Special Edition, Skyrim Anniversary Edition and Skyrim VR
      So far all versions of DynDOLOD use the SKSE plugin PapyrusUtil for the optional dynamic LOD in the game. Starting with version 2.45 there is now the alternative DynDOLOD DLL available.
      The current DLL version is 2.45. It works with dynamic LOD generated by DynDOLOD Standalone 2.45 and newer.
      Read the ..DynDOLOD\Docs\DynDOLOD_DLL.html included in DynDOLOD Standalone for an explanation about DynDOLOD DLL, installation instructions (overwrite papyrus scripts of DynDOLOD Resources) and how it works.
      If there are problems with it, check DynDOLOD_DLL.html and the DynDOLOD FAQ first before posting.
      If a DynDOLOD.DLL version is required for a game version that is not listed below, request it in this thread. First, search this thread if it has been requested already, though. The future will tell how long it takes to release updates.
      Typically a new DynDOLOD.DLL is required for each new game version, but not each new SKSE version. For example a DynDOLOD.DLL compiled with SKSE64 2.0.9 also works with SKSE64 2.0.10 for the same game version.
      Nexus Downloads for DynDOLOD 2.45 and higher
      DynDOLOD DLL for Skyrim
      DynDOLOD DLL SE for Skyrim Special Edition
      DynDOLOD DLL VR for Skyrim VR
      Mega Mirrors:
      DynDOLOD.DLL + Scripts for Skyrim 1.9.32 (overwrite the papyrus scripts included in DynDOLOD Resources)
      DynDOLOD Scripts for Skyrim Special Edition and Skyrim VR (overwrite the papyrus scripts included in DynDOLOD Resources SE)
      DynDOLOD.DLL for Skyrim Special Edition 1.5.39
      DynDOLOD.DLL for Skyrim Special Edition 1.5.50
      DynDOLOD.DLL for Skyrim Special Edition 1.5.53
      DynDOLOD.DLL for Skyrim Special Edition 1.5.62
      DynDOLOD.DLL for Skyrim Special Edition 1.5.73
      DynDOLOD.DLL for Skyrim Special Edition 1.5.80
      DynDOLOD.DLL for Skyrim Special Edition 1.5.97
      DynDOLOD.DLL for Skyrim Special Edition 1.6.318
      DynDOLOD.DLL for Skyrim Special Edition 1.6.323
      DynDOLOD.DLL for Skyrim Special Edition 1.6.342
      DynDOLOD.DLL for Skyrim Special Edition 1.6.353
      DynDOLOD.DLL for Skyrim VR 1.4.15
    • By saldas
      Hi, I've a simple question. I've been using Skyrim LE and ENB version 472, as ENBoost. Previously was using a GTX 1070 ti, and always the red text message showed up on game start, telling me that no graphics modification was possible - but then I was only using it for extra memory.
      Now I've upgraded to an RTX 3080 12gb, and it's a fresh install of Skyrim. The red text no longer appears. The white text with ENB version etc does, as before. Does this mean that ENBoost is not working as intended?
      EDIT: Sorry, this question shouldn't be here. Silly me, forgot that there's an option I didn't change in enblocal.ini.
       
  • Recently Browsing   0 members

    No registered users viewing this page.

×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.