Warning to modders: avoid redefining "region_settings"

Many mods use "type": "region_settings" structure.
This json is pretty huge and redefines a lot of things. It sometimes just needs to be changed. Because of the old code it uses, lack of examples (other than core), sheer size, and some weird practices, maintaining backwards compatibility of this structure isn’t always as straightforward as it looks.
This means high chances of things breaking if you redefine it.

Instead, if possible, use "type": "region_overlay", like in DinoMod. Redefine only things that you need redefined.
While this won’t always warn you that things aren’t working, they will still get default values instead of kicking you back to main menu.

Changing “region_settings” in the core necessary if we want to have reasonable cities, biomes, weather etc. so expect it to be disturbed once in a while. Not without warning, but the warning will usually be a PR on github, not a message on forums (like this one).

Example from DinoMod:

[
   {
      "type": "region_overlay",
      "id": "dinomod_overlay",              "//": "unique identifier for this overlay",
      "regions": [ "all" ],                 "//": "A list of regions to which this overlay should be applied",
      "city": {
          "parks": {                        "//": "weighted list for park overmap terrains",
              "fieldoffice": 1
          }
      }
   }
]