Motivation / Problem

The SettingDesc structure has two strings for the name. One directly in SettingDesc and one in its contained SaveLoad. For all intents and purposes the string in the SaveLoad is (going to be) the same as the one in the SettingDesc; there is code to copy the name from SettingDesc to SaveLoad when the SettingDesc name is not empty.

So, only when the name of a setting is empty SaveLoad's name is actually used. Setting a name for those few ones with an empty name means we can just write the Setting name in the SaveLoad's name field and stop copying the SettingDesc name to the SaveLoad at a later time.

Description

• Name the unnamed settings.
• Create an accessor for the name of a setting.
• Remove the name field from SettingDesc and save than name in `SaveLoad``.

Limitations

None.

The name of five settings is changed, including in the compat layer. However, these are only used for old savegames so setting these names has no effect on savegame compatibility.

Checklist for review

Some things are not automated, and forgotten often. This list is a reminder for the reviewers.

• The bug fix is important enough to be backported? (label: 'backport requested')
• This PR affects the save game format? (label 'savegame upgrade')
• This PR affects the GS/AI API? (label 'needs review: Script API')
  • ai_changelog.hpp, gs_changelog.hpp need updating.
  • The compatibility wrappers (compat_*.nut) need updating.
• This PR affects the NewGRF API? (label 'needs review: NewGRF')
  • newgrf_debug_data.h may need updating.
  • PR must be added to API tracker