[Suggestion] Steam workshop: Mod incompatibility notice

[Jace ∅ Ethaniel]

Suggestion:
Add a feature to mod pages that allows the mod author to define mods that are incompatible with their mod, and notify the user when they attempt to subscribe to a mod of this incompatibility.
It would not need to be on both ends (both conflicting mods) to work, just a simple check much like the mod dependency notice: "Hey, these mods are incompatible with this mod"

From a users perspective, this would help me steer away from mods that are not compatible with the ones I already have (or even to a patch that would make it work).

From a mod developers stand point... OMG, PLEASE PLEASE PLEASE add this feature!
This feature would reduce occurrences of "My game broke, it's your fault!" and help mod developers help users who legitimately need assistance instead of having to constantly tell people "read the description" or "This mod isn't compatible with that mod," or ignoring them and getting a bad review because "your mod sucks and it broke my game" (when really they didnt read the description). A lot of users just glance over the description of a mod (which is currently the only place incompatible mods can be listed) assuming they read it at all (some just look at the name and hit subscribe). Some users have so many mods that they cannot remember all the mods they have and if they are incompatible with "X-mod-that-adds-stuff-they-want." We dont really need a place for patches that make "X" mod play well with "Y" mod because they can be listed as dependencies.
I know a lot of devs may not care enough to suggest it, or perhaps they dont run into the issue because of how the game handles mods, but in starbound one of the most common issues users encounter is with the haphazard subscription to "All the mods ever" without really going through their mod list to see if, maybe, they already have a mod that affects the same thing that mod is changing. It would require a little more effort on the mod developers side, but once set up I am absolutely positive it would help users (especially those with 500+ mods...).

[Zekiran]

Most Nexus mod makers already do this.

It's not really up to Steam to patrol the contents of literally every game's mods, and which ones might or might not be compatible. It's up to the user and if you're lucky the mod maker, to have tested their mod with at least the major pieces of used mods on the game.

[Jace ∅ Ethaniel]

You didn't read what I said so I will point some things out for you.
1) It is a feature mod devs would use to specify incompatible mods, not steam themselves; like how mod devs add mods that their mod depends on. Steam doesn't "patrol the contents of literally every game's mods" to see which mod is dependent on which mod, and so Steam would not "patrol the contents of literally every game's mods, and which ones might or might not be compatible."

2)The Nexus has nothing to do with the Steam Workshop, you can't subscribe to a mod through steam (thus getting auto updates and such) using the Nexus; though the nexus is good for games like Skyrim and Fallout 4, it is not good for games like Starbound (which has the majority of its mods on the Chucklefish forums and steam workshop).

[Zekiran]

That's exactly why I said what I said: it is up to the developers of the mods, not steam nor any other party.

Mod makers are not the game devs, and they are not beholden to any rules about how they do what they do.

The nexus operates as a much more streamlined version of the Workshop, in case you didn't notice it's been around that long and has a lot of practice (albeit they have broken everything with their stupid new process, so... there's that). I use it as an example. Here on the workshop, only a scant few modders do this.

Again: it's up to the mod maker, not any other entity, to do this. And it is on the user to research everything they download - just like any product, program, or online activity. If comments keep saying "well it doesn't work with x thing" but the maker of the mod doesn't reply, then what? Obviously the mod doesn't work with x thing, so... gotta research.

[Jace ∅ Ethaniel]

You are not understanding at all. I just want steam to expand the functionality of the already present "dependencies" feature to include "incompatibilities".

Stop your pandering to Nexus mods. I dont care about nexus mods. Nexus mods is not good for the games I play like Space engineers and Starbound (sure it has Starbound support, but all the mods there suck/are out of date).

You keep saying it is "up to the mod developer" to define incompatible mods but you fail to notice that WE CANT. All we can do is put it in the description which people hardly read! I am simply asking for a very simple-to-implement feature that would allow Mod developers to mark their mod as incompatible with certain mods, in order to ease the burden on mod developers for support requests. Sure, it would be GREAT if users did the research to make sure that "x" mod they want doesn't conflict with one of the other 500+ mods they have (YES, in STARBOUND there are people with that many mods!) but the likelyhood that they will remember that they have "Y" mod that does the same thing that "x" mod does is unlikely. It doesn't take much effort at all on steams part to implement this. You are acting like this feature would be overly cumbersome to Steam, when really it would HELP steam by reducing the number of messages users post because of mod incompatibility crashes/issues thus reducing the number of messages the steam servers have to handle/store; not to mention how it would benefit the users and the mod devs! Seriously, a small dialogue box that says "Hey the mod developer says these mods don't work with his/her mod" is not hard to implement.

Your arguments are not valid. Not every game HAS Nexus support, not every game NEEDS Nexus support. How about you leave with your unhelpful Nexus pandering?