Blacklist updates do not propagate to users who already have config.json about cp77-bettersleeves

[Taudris]

I think the least intrusive solution would be to have a JSON property that contains the full set of default blacklisted items that was known by the last version to write the config. If that property is missing a default blacklisted item, then add that item to the user's blacklist.

So for example, if a user has this config.json (note that mantis_blade is missing):

{
  "rollDownWeaponBlacklist": {
    "projectile_launcher": true
  },
  "rollDownWeaponDefaultBlacklist": {
    "projectile_launcher": true
  },
  "rollDownDelay": 1,
  "rollDownItemBlacklist": {
    "outfit_01__q305__hazmat_": true
  },
  "rollDownItemDefaultBlacklist": {
    "outfit_01__q305__hazmat_": true
  },
  "autoRoll": true
}

And init.lua has this:

function BetterSleeves:ResetConfig()
    self.autoRoll = true
    self.rollDownDelay = 1.0
    self.rollDownItemDefaultBlacklist = {
        ["outfit_01__q305__hazmat_"] = true,
    }
    self.rollDownItemBlacklist = self.rollDownItemDefaultBlacklist
    self.rollDownWeaponDefaultBlacklist = {
        ["mantis_blade"] = true,
        ["projectile_launcher"] = true,
    }
    self.rollDownWeaponBlacklist = self.rollDownWeaponDefaultBlacklist
end

You can identify that the user's rollDownWeaponDefaultBlacklist does not have mantis_blade in it, and therefore it needs to be added to their rollDownItemBlacklist.

[Marco4413]

Sorry I didn't respond earlier. I have already thought of a possible solution, which is adding a version to the config file. That will allow me to make even bigger changes to the config file and still being able to migrate from older versions. Thanks for the tip though

[Marco4413]

Should be fixed with 713ca30