My concern with this approach is that the locale files are not specific to each mod. There's a reason why the current setup has you specify the setting name in it. All fair points. I think curiosity's suggestion doesn't have that issue, so again I would be fine with that. Just so I don't need hundr...

E.g. add a field localised_allowed_values to the string setting prototype. If specified, it must be an array of LocalisedString the same length as the allowed_values array. The localized names are matched to the values in order. Sure, that would work too. It would be a little more work for a mod au...

Problem When creating localization for mod settings, you can create locale strings for specific string-setting values. Quoting the wiki ( https://wiki.factorio.com/Tutorial:Mod_settings#Locale ): [string-mod-setting] #<setting-name>-<dropdown-item-name>=<translated dropdown item> my-mod-string-test...

Not showing for me either. Should note that from 0.16.51 to 0.17.0 didn't work and I had to upgrade manually, but 0.17.0 to 0.17.1 worked just fine. Now that 0.17.2 is out, it seems that all 0.17.X versions are missing from the list again.