add new info.json dependency type: incompatible

[nucleargen]

New dependency syntax may be like "! mod_name" in dependencies array.
This would be useful if mod have permanent incompatibility with other mod and user cannot launch this mods together.

At now this problem resolving partially by specifying optional dependency like "? mod_name < 0.0.1" - no mods have version below this. Then if i enable mod specified in this way - my mod becomes red in list. But: this dependency in deps list are always red which not provide clear information to target user.

[bobingabout]

if it would be possible to specify a not compatible, then... I'd use it. Maybe not right at the moment, but there are times in the past where I wish I could have used it.

[Gangsir]

This would be useful for mods that step on each other's toes, IE change or add a very similar thing.

[eradicator]

I would also very much welcome some more flexibility for dependencies. The addition of an "incompatibility" category would be a great step in the right direction.

Ultimately i would love to have full support for the three basic logic operations NOT, AND and OR though which would make arbitrary conditions possible while keeping the current syntax valid:

• At least one mod that adds a specific material (e.g. "gold-ore"):

  Code: Select all

  "(modA > 1.0.0) OR (modB > 1.0.0) OR (modC > 1.0.0)"

• Two mods that are useful in conjunction but not seperate:

  Code: Select all

  "modA > 1.0.0 AND modB > 1.0.0"

• A specific mod version range:

  Code: Select all

  "modA > 1.0.0 AND modA < 2.0.0"

• Incompatible mod:

  Code: Select all

  "NOT modA"

[justarandomgeek]

As a slightly evil hack, you can make an optional dependency on a version *FAR* in the future (like 99.99.99 or so), and your mod will be disabled if the other is present.

[Rseding91]

This was added in 0.16.0.