While working on the settings system a bit I noticed that there is a conflict in CSettingList. It uses and to specify the minimum/maxmimum number of items in the list. But the same tags are read by the setting definition (e.g. CSettingInt for a setting of type "list[integer]") and used for the minimum/maximum value of the setting. Obviously this leads to unexpected conflicts.
I renamed the and tags of CSettingList to and to avoid this problem.
settings: fix conflict of <minimum> and <maximum> for CSettingList
@Montellese any reason this needs to be Gotham?
There's no setting right now that runs into this conflict so it's not a 100% must. But it certainly is a bug.
Ok. jenkins build this please.
@jmarshallnz: Does this mean Gotham or Gotham + 1? Just so I can adjust the label and milestone on the PR if necessary.
Should I make a pull request against Gotham or will you cherry-pick the commit?
Up to you :)