Disable all mods in campaign

[CzBuCHi]

TL;DR

Campaign should be played as devs intended and not with mods.

Why ?

Some mods may change game entirely and i think, that campaign need to be played as devs intended ...

Also when mod adds new ore and changes recipe for basic items campaign becomes unplayable ... (for ex. Bob's mod changes yellow belt to require Tin ore which player obviously cannot mine on campaing map ...)

[Rseding91]

Last I checked the campaign was meant to error if it detected you started it with any mods. Thus preventing you from playing it with mods.

[eradicator]

Last I checked the campaign was meant to error if it detected you started it with any mods. Thus preventing you from playing it with mods.

Check again.

[Rseding91]

Checked as in talked to the campaign guys about possible solutions. Clearly they didn't implement it yet.

[abregado]

agree, but havent implemented yet. Solution not yet designed.

[QGamer]

This sounds like a very interesting idea:

1. Will this work for scenarios in addition to campaigns?
2. Can this be used to allow some mods but not others?

[ssilk]

In practice it maybe runs into this solutions:

A. We have Mods-Sets
B. We have Mods-Filters

A explained: A mod-set is what is basically stored in mods.json: Just a list of mods. Such a list can be part of a map, or the player can store such lists himself to exchange mods fast or keep old mod-versions to replay older games.

Be also inspired by https://docs.npmjs.com/files/package.json#dependencies
That is how npm handles version-updates of mods. Just an idea.

B explained: Mod Filters are also a list of mods, but include information about how that list should compare the current mods and if it should add or remove mods. Thinking of white/black-listings of mods. Like

Code: Select all

ALLOW {
  ! ALL            // no additional mod allowed
}
ADD {
  MOD1, MOD2, MOD3 // a list of mods
}
REMOVE {}