It's a 150kb file that just contains a .pdf with the install instructions, no other files, and which the Nexus also cleared as safe--that's definitely a false positive. And not the first I've seen from Windows, either. It seems like some small files with the .7z filetype cause threat assessments like this, but I just replaced it with a .rar archive and there's no warning for me on my end now. Try it on yours.
Wait, I am confused. Is this supposed to be a download containing all the mods? Cause when i downloaded, I just got a pdf showing a list of mods. Is that supposed to it?
Correct. This isn't a pre-compiled pack, partially because that's not permitted by modders but mostly because the mod builds seek to be modular. A single download of all of this content wouldn't let users pick and choose what they want to use, or slot their own content in, which is one of the main goals of the mod builds. The mod builds provide a set of thematically consistent, vanilla-friendly, and most importantly guaranteed-compatible content complete with custom compatches, but the install process is left to the user in case they want to make modifications to the setup.
Yeah but 52 pages of mods, to download and install 1 by 1 because modders don't permit what.. they are changing the assets of a copyrighted game, they gonna complain? Let them grow up, but I'm not gonna spend hours literally just to mod and old game. I'd just install community patch and that's it, but someone could upload a ready to use compilation of the best mods, mods that don't alter the gameplay.
Make it yourself, then, if you want. I won't do such a thing. One of the primary goals of the mod builds is modularity, and I would keep the mods separate even if modding rules permitted combination.
Hey, I just wanted to offer up my thanks for this collection and your effort. I love your vanilla-plus approach and having all the info in one place with an informed curation has made it a very enjoyable return to a great game.
As someone using Android without access to a PC, are there any work arounds for the mods requiring TSLPatcher? Scrolling through some of the mods I can see how creating exe installers for windows users is a definite time saver, but is it possible to recreate what those executables do manually? Does TSLPatcher essentially just streamline the process of moving files where they need to be, or does it actually amend/create files on the fly, making it harder to recreate? I have quite a bit of experience working with mods on a handful of games and know that sometimes a work around isn't always possible, I just wanted to see if you might be able to point me in a helpful direction.
Not really, and because that's not very satsifying (or helpful) to you, I'll explain why.
The TSLPatcher isn't just a convenience installer, it's probably the most important single tool for mod compatibility. The TSLPatcher doesn't just take files and move them, as you suggest it dynamically edits existing files and in some cases even generates files from scratch during the install process, just based on data input to its changes.ini file, which is what controls its processing. Without the TSLPatcher, there would be no way to make automated edits to files which other mods have already modified, which would de facto require endusers to not just apply conflicting file changes by hand (for instance, opening up a module file, manually tracking down the .utc data a mod uses, and inputting all that data piece by piece, because otherwise you have a hard overwrite of the base module file), but also know how to do all that, because it's not as simple as a text editor. A lot of these filetypes can only be cracked open by an array of community tools, which are often finnicky, to put it politely. And then that brings us back to square one, with do those programs work on a mobile device?
So all that said, technically speaking if you wanted to get really caveman with it and you could get the tools you needed working on your phone, you could go in to a given TSLPatcher's changes.ini file, isolate the exact modifications it makes, open the effected files up, edit in just those changes and preserve other mods' changes in so doing. But you'd need to do that for every single file that has conflicts across every single TSLPatcher install, and due to the scope and complexity of the K1CP alone, that would likely take, at minimum, hundreds of hours to do. So back to 'not really.'
There was a project to get a stable version of the TSLPatcher working on mobile, but sadly it appears to have been abandoned and was never properly functional for even its most basic features.
17 comments
Here's the 'Learn More' link.
As someone using Android without access to a PC, are there any work arounds for the mods requiring TSLPatcher? Scrolling through some of the mods I can see how creating exe installers for windows users is a definite time saver, but is it possible to recreate what those executables do manually? Does TSLPatcher essentially just streamline the process of moving files where they need to be, or does it actually amend/create files on the fly, making it harder to recreate? I have quite a bit of experience working with mods on a handful of games and know that sometimes a work around isn't always possible, I just wanted to see if you might be able to point me in a helpful direction.
Thanks
The TSLPatcher isn't just a convenience installer, it's probably the most important single tool for mod compatibility. The TSLPatcher doesn't just take files and move them, as you suggest it dynamically edits existing files and in some cases even generates files from scratch during the install process, just based on data input to its changes.ini file, which is what controls its processing. Without the TSLPatcher, there would be no way to make automated edits to files which other mods have already modified, which would de facto require endusers to not just apply conflicting file changes by hand (for instance, opening up a module file, manually tracking down the .utc data a mod uses, and inputting all that data piece by piece, because otherwise you have a hard overwrite of the base module file), but also know how to do all that, because it's not as simple as a text editor. A lot of these filetypes can only be cracked open by an array of community tools, which are often finnicky, to put it politely. And then that brings us back to square one, with do those programs work on a mobile device?
So all that said, technically speaking if you wanted to get really caveman with it and you could get the tools you needed working on your phone, you could go in to a given TSLPatcher's changes.ini file, isolate the exact modifications it makes, open the effected files up, edit in just those changes and preserve other mods' changes in so doing. But you'd need to do that for every single file that has conflicts across every single TSLPatcher install, and due to the scope and complexity of the K1CP alone, that would likely take, at minimum, hundreds of hours to do. So back to 'not really.'
There was a project to get a stable version of the TSLPatcher working on mobile, but sadly it appears to have been abandoned and was never properly functional for even its most basic features.