Mod portal and config.lua approach

[binbinhfr]

Hi,

while updating my mods, a user said something quite true : with this mod portal approach that will update mods automatically, and possibly (in the future) load/unload them automaticaly according to map requirements, the customization of mod using a config.lua approach will be hard to keep, because the config.lua will be overwritten at each install/uninstall from the portal.

So I wonder if devs could think about another way to allow mod customization using some king of an INI file. It could contains section for each mod, containing keys that could be readable by an API function read_config(keyname), that would return nil if no key is defined in the INI file. This read_config(keyname) could be accessed from data.lua and control.lua.

But to avoid MP desync, this INI file should be consistent between players. We should find a solution for that.

Because we must take into account that, in MP, a lot of admins are tweaking mods before installing them and sharing them as a modpack requirement...

[Supercheese]

There's already been good discussion about that here: viewtopic.php?f=28&t=26166

[binbinhfr]

thanks for the info, I missed that one !