Dependencies: IsIncompatible ?

[Ralzar]

As more mods keep appearing and some mods take over for abandoned mods etc, this will probably start popping up more and more: Mods that are incompatible.

Is there a way at the moment to code this into the dfmod.json to have the mod list produce an error?

If not, might it be an idea to add a value for "IsIncompatible" that you can set to true? So users get informed if they are trying to use two mods that will create issues?

Or an alternative to "Dependencies" called "Incompatibilities" with its own set of values? So you can specify specific versions of mods that are incompatible with your mod?

[Hazelnut]

Is there actually an instance of this?

[BadLuckBurt]

I can see this being abused if two mod makers end up hating each other.

The other guy is such a prick that I will make his mod incompatible with mine by flagging it, mwuhahaha that will show him!

And what if a modder actually makes their mod compatible after a while but the one with the Incompatible flag isnt updated?

Lastly, what about freedom? Let me break my game in peace

[Ralzar]

Haha, true.

I actually handle this at the moment by having my mod set to be loaded after mods it is incompatible with, then when ingame it does a popup to tell you about the incompatability.

So you could do "I don't think you should use that mod, because the author is a dick!" ingame

[Kokey]

It can't really be abused if DFUnity only warned that X was incompatible Y, not prevented the use.

[pango]

They're many ways pieces of code can break one another in more subtle and hidden ways, I wouldn't spent too much time on how such feature could be abused.

Just make sure it works (for example, as explained before, that a module describes another module as incompatible, it has to be restricted to some versions so the other module's author has a way out if he/she fixes the incompatibility;...)