0neGal

Any reason for dropping support entirely over just changing which one it uses by default?

> ... but not sure how mod managers will react to those files missing from release zip. For Viper, we actually just write the file when changes (settings) are made...

I specifically and intentionally did not implement this, as I easily could've. Not only would this cause quite a bit of network traffic since it's not unlikely 5-10 mods are...

I'll try and have a look at it, another issue with config files is, what if a mod adds a new setting? That setting won't get auto added because that'd...

Not possible, some mods use `.nut` scripting files, parsing those is not something we can or should do. `.json` config files can be parsed however and be merged.

> An update check and option to update right in the mods view would maybe be a nice alternative. I'll have a look at this at some point, as it's...

To be quite frank, I've never actually used GitHub Actions, and have no clue how to set it up, but I'm open to implementing/setting it up... I'll try to look...

There is an `excludes` array in your `viper.json` which you could add it to. I'll just add these files to the defaults, which would implement it. I was mostly unaware...

> Like are they all in `mods/My.Mod/cfg/` folder, or all named `*.cfg` (`mods/My.Mod/**/*.cfg`)? To my knowledge everything is in `/cfg`, but the actual file names can be anything from `.json`...

> @0neGal do you have enough rights to transfer this issue over or should I make a new issue in https://github.com/flathub/com.github._0negal.Viper ? ^^ I do not nope... :p