In response to post #43223160. #43223235, #43225810, #43226065, #43226570, #43226580, #43226675, #43226930, #43227145, #43227835, #43229000 are all replies on the same post. @ Moriador While I can't speak to using the CK with MO, because I haven't used it, I can say that what you described is what I think most of the problem with MO.... people don't understand it so they don't like it. How I came to understand it, was that MO "injects" a mods assets into the game's DATA folder when a mod is activated without actually writing it there, and possibly overwriting a file that is already there and permanently breaking a game. You are ALWAYS using the clean backup of your DATA folder because you never change it.. The reality is, when you use MO, every mod you install creates a folder with the mod's name (e.g. Steamapps/Skyrim/ModOrganizer/mods/modxyz) and all of the assets are extracted there instead of your game's actual DATA folder. You then simply "activate" a mod when you want to use it, or deactivate it if you don't. You have total freedom to go into the mod's folder and change or delete files at will if you please, either through MO or with Explorer. There is also a nifty function to "hide" a file in MO so it won't be used without deleting/destroying it.(great for texture/sound mods when you want to use some parts of 1 mod, and some parts of another mod) While this all might be moot at this point, because who knows how the new tool is going to work, I hope I made the MO virtualization make a little more sense. Yes, you launch your game from within MO, but I did the same with NMM, so it didn't bother me.