nokturnihs

You make a valid point however it's probably not an extreme expectation to require a installation guide for public collections and I don't think that would constitution content moderation. It also probably makes collections more attractive. Look at the popularity of STEP in Skyrim as an example. Very successful and it's a good presentation that would probably draw more interest in the feature.

There was some typos there because of the mobile site but mod authors cannot opt out of collections and the rest should be fairly lucid.

My most basic proposal would be to require two things for PUBLICLY viewable collections - a mandatory installation guide to cover whatever manual edits or suggestions/options the collection author/maintainer has and an acknowledgement that at the very least states "by making his collection visible to the public i certify that using a default installation the mod collection in question works without further actions or If it does require manual installation steps I have outlined them in the guide. Should that be proven false i acknowledge that the nexus may publicly delist or remove the collection until it meets these requirements." For people interested in sharing private collections with friends when they do not want to meet those requirements they can create it privately with a private link to share and edit or troubleshoot it and make it public later. That way everyone still can handle it how they like and no one is restricted heavily but there's at least some burden of responsibility to collections maintainers to certify it's ready for public consumption and doesn't (like at present) have such detailed information as "mods that work" when clearly some do not "just work". It protects end users a little more and offers some CYA to the nexus and also adds less burden on mod authors who could easily become overwhelmed by support requests. This was one of the big contentions over collections. Personally I feel like collections authors should carry support burdens as they're unable to opt out of collections for their works. That will never happen on the nexus for various reasons so this is at least something that might help MA's out a little.

your feedback was nothing more than an entitled rant. my reply was designed to point out obvious flaws in your "feedback", namely accusing nexusmods of stealing intellectual property from mod authors - which, honestly - if you get that wrong - should disqualify the rest of your feedback from being taken seriously. the rest of your word salad and subsequent response is just gibberish and so full of holes and inaccuracies it's not even funny. also, i don't need your modding "cv". you think it gives your word salad some sort of credence? it doesn't. I disagree. It seemed to me you were employing fanboi defense mechanics and trying to shut down a narrative because it didn't align with your emotional devotion to the product in question. Again I'll point out that if the purpose of your reply was to protect your emotional investment in nexus collections it serves absolutely no purpose in regards to improving the collections feature. If anything there's a sense of entitlement from the fanbois who cannot ever accept any kind of negative feedback or criticism at all on "their thing" without engaging in bullying tactics. Last my "modding cv" was to point out I'm well aware of the technical aspects you initially inferred I was too stupid to understand, which was what you intended to infer and was incorrect in your assumptions. It wasn't to impress but to instead invalidate your harassment. I'm sorry my ability to communicate at length on a topic intimidates or frustrates you (word salad).

The comment about comments you are right. It's less obvious than a traditional mod listing but comments are there. I found it later and didn't go back and edit. The 99*99 was a typo. It is 99+99 for that particular collection. I maintain my position that it doesn't incentivize people going premium. And your argument that the reason FOMOD installers are a thing is because BGS modders made them is far more ridiculous considering scripting and automation of executions existed since the days of ATARI Basic - it's just scripted input and I'll point out several CP2077 mods already do this though not all. Nexus absolutely should have that functionality built-in as part of their collection feature. Or at least require an installation guide for posting collections publicly so that incompetent collection "authors" aren't negatively impacting the collection experience.

So my topic post was to provide feedback for the Nexus to improve the feature. I was providing positive and negative feedback and offering considerations for the nexus devs to consider. I'm not sure you understand what feedback is used for based on your reply.... To a degree they did in fact lose creative control over their mods which is why I said "in-part" but that was probably unnecessary color on my part. Yes I did leave feedback on the issues in the collection and left feedback on the collections feature so both can potentially be improved. Of course I can still mod it one file at a time, that wasn't the point - the point is that if this is being billed as a way to make modding more accessible a basic level of functionality should be required to post a collection - mainly going to the effort of writing some form of post-install script (even a .bat file would do) that makes the mod functional on at least a basic level. It isn't rocket science and it a significantly simpler operation than the bar free users are expected to perform to use said functionality. And yes, I realize the basic functionality differences here between free and premium users. It's a lengthy process and while I'm sure as a premium user it's much smoother - the current implementation isn't encouraging people to go premium or if it is, it's a predatory means of doing so. I also realize it's modding - in and of it's nature there's gonna be crashes, gonna be bugs. the difference is KNOWING a collection, under a default installation without any additional input from a free OR premium user will 100% cause a game to CTD and having absolutely zero QC to ensure that installing a collection should at least boot the game or make the mod installation process simple for people new to modding (the intended audience). I've been modding games for 20 years. I've written mods and made many edits to mods in many different games. I can and do install my mods without issue. I tried this feature to see if it functioned as advertised or even came close - as an experiment to see what it was like in a separate modding profile. Most of my non-IT friends cannot and might look at collections as an option to embrace modding but as the feature exists at present - it's either going to drive them away from modding for good or I'm gonna be the one fixing their mod installations because the collections "author" could not be bothered to make a script to clean up the manual installation process (pretty much every game has at least a few manual mod installation steps - something easily corrected with a simple bash/.bat script most the time.) As the feature stands one could absolutely create collections in droves with the sole purpose of causing games to CTD which would change the narrative or perception of this feature to the outside world. I don't think anyone wants that but there's nothing stopping this at the moment and as detailed above it's easy enough to do by accident. There's no accountability to the collections "authors" and it's still modding.... but maybe there should be? Mod Authors are held to a certain community standard to support their mods and creating mods is significanlty more challenging than throwing together a collection. I'll also point out it's not exactly a new thing having post-install or secondary setup scripts in the modding space - Minecraft is just one example that's been doing this for years and years - and if vortex isn't capable of running a .bat file to remove extra files from a collection install then that's a function that should be considered. If collections "authors" can't put together a script to do that I don't know that the collection should be publicly accessible until a basic "functional" state can be reached in the process. It's one thing to share mod collections with your friends and walk them through the special extra steps, another is to put out an incomplete process and not even bothering to write out a guide on completing the installation steps that aren't automated via this feature.

Hi, So - despite my personal distaste for the changes to the nexus policies implemented to make way to try out collections I tried out the collections feature on Cyberpunk 2077. Pros: - It did install all the mods. - It was a way to discover mods I'd previously failed to notice. Cons: - It took forever as a free user (99-clicks to be precise as that was the number of items in the collection) - the end result is a game that WILL CTD as soon as I launch it because no post-installation script to clean up the installation and actually... finish the installation of the modpack was performed. My feedback: - Collections were billed as a way for non-computer savvy folks or folks new to modding to be able to enjoy many mods easily. Mod Authors were required to forego their intellectual property rights to a degree to make this feature happen. Why then are you allowing collections to be posted that will result in MORE problems than if a person were to simply install a few suggested mods from say a youtube video. It seems to defeat the intent and cause more problems than it solves. - Why are collections being posted that will 100% break people's games unless they're going in and performing manual file changes, which, while briefly discussed by Vortex in the form of alert boxes, large collections requiring 20-40 manual file edits to make the modpack work is ridiculous. - Why isn't it a basic requirement that collections authors, once the install is complete have a fully configured modpack or at least provide options for collections installers to go through (like a FOMOD installer)? - With the simple fact that as it stands collections are shipping incomplete and broken with zero liability for collections authors, absolutely no direct way to see comments BEFORE installation and zero effort in regards to verifying a mod collection in fact functions, why is it even an option. I've created mods and mod edits in the past. While I've spent very little time familiarizing myself with Vortex's back-end capabilities having a method to run post-install collection scripts to make a collection function should be mandatory - at the very least to clean up unused garbage left over from the installation to save in disk for the end user. I'll also point out that as a free user clicking 99*99 times to download a collection that doesn't function certainly does NOT inspire me to pay for the privilege of downloading a little faster a mod collection that does not work. Nexus - If you want people to go premium and after the way you bend modders over to make collections happen, you need to at least make a feature that doesn't break game installs and currently that's what you're allowing to go up in collections.