Okay, so who does this not break for? It looks like earlier versions install that broken config too; if I delete it, it just gets replaced again with the broken config. So for a significant number of users, newly created nether worlds, and worse, newly created chunks in existing worlds, are being created with no ores.
Can the devel team fix this? They should do something like, at startup, check the config file and if it contains any entries where XXXMinY==128 && XXXMaxY==128, then remove both entries and let the mod fix them up.
Also, should this config not be fixed up to make more sense? I'm not sure all of the ores should be spread across the entire height range. IMHO They should probably at least partially match what happens in the overworld.