USING SSEEDIT TO ENSURE ORDINATORE TAKES PRIORITY UPDATE
When programs update files there are two approaches: One is to replace the existing file with a new one (typically by deleting the old one and writing the new one in its place). Hard links mean that Windows has two filenames that both point at the same underlying storage. Vortex syncs your mods by making hard links from its modules folder to the data folder. It's change detection is also incomplete, necessarily due to implementation details: Vortex (at least when I used it) left NEW files laying in your data folder, with no way to clean them up. Example, if you use Notepad or NifSkope you won't get option to restore, while with 圎dit you should get option to restore plugin, even if you didn't create backup in 圎dit. For edited file it depends on the tool used if you get option to restore or no option. With Vortex if you do the same, if tool deleted file you should get a warning next time you deploy with "External Change" and an option to restore the deleted file.
If you run a tool through MO2 that changes or deletes a mod-added file, this changes or deletes the mod-added file and the only way to get back original file is to re-install mod. \> You will never overwrite anything important If you mean the /mods/ folder, the only real difference between MO2 and Vortex is Vortex for installed mods uses exactly the same name for directory as the mod-archive (except extension), while MO2 as directory either uses the suggested name or whatever you've typed-in yourself.Įxample, while MO2 normally calls directory "Unofficial Skyrim Special Edition Patch", Vortex calls directory "Unofficial Skyrim Special Edition Patch-266-4-2-6a-1636838663", since you downloaded the mod-archive named `Unofficial Skyrim Special Edition Patch-266-4-2-6a-1636838663.7z` >The folder system of mo2 is just superior in my opinion.
0 kommentar(er)
