Because currently the idea involves having two copies of TSL, or taking a look at the altered files in each mod. My current method is a bit ham-handed so I'd like some experienced opinions on the topic of what the most commonly altered files are. The needed merges happen, and the game files are swapped for the modded ones at runtime. (I've made a custom 'mod' for this purpose, which is pretty much just the empty game folder structure) Then install any mods I'd like to try out/use into the folder. At the moment I copy over much of TSL's game content to one of my mod folders.
My idea involves treating a subscribed mod directory as a 'main' game directory. So TSLpatcher's primary feature would be merging, something the workshop clearly lacks.
(Atleast this has been the case as far as I have seen) Additionally steam doesn't verify the content of these folders unless there is an update (in my week or so of testing it atleast), which means you could change the content of the folders, and they stay that way. Steam also doesn't seem to automatically delete the files of unsubscribed mods, when unsubscribing, rather leaving them in the workshop content directory. This is a novel idea which keeps the game files clean and mods easy to uninstall/delete. I've also noticed that steam doesn't modify the game files in anyway when installing mods, rather opting to 'mod' the game at runtime. I've seen that because there is a lack of merging support in the functionality of the steam workshop, much of the mod content requires merging is unlikely to find it's way onto the workshop. So I've been playing quite a bit of TSL again after the steam version got it's widescreen update, and as a consequence have been downloading a whole host of mods both from here and from the Workshop: Which brought me to an interesting idea using the workshop.
0 kommentar(er)
