This means that new SPADS installations will now have these basic presets already defined by default.These presets use the new preset inheritance functionality so that settings declarations are factorized as much as possible, easing maintenance.
As autohost administrator, you can start from these presets and enrich them as you like to add game-specific tuning (especially for the battle presets, which may need some modoptions to be adjusted for duel mode for example).
- The convention I chose for these new presets is to use upper case preset names for "full presets" (i.e. presets defining all possible settings) and lower case preset names for "partial presets" (i.e. presets defining only a subset of the settings). This means for instance that doing "!preset duel" will keep current configuration regarding unrelated settings (like "autoBalance"), whereas doing "!preset DUEL" will reset all unrelated settings to the default value at the same time (if changed previously, "autoBalance" will be restored to default value for example). As only "full presets" can be used as defaultPreset, when you use this convention you know you have to use the upper case preset names for default presets. However this is only a convention, you can change all this and follow your own rules.
- The new preset inheritance functionality makes it really easy to organize and declare as many presets as you want. A good practice is now to keep the "default" preset included by default when installating SPADS unchanged, and create your own new preset inheriting from the "default" preset, containing the changes you need. Then you only have to set this preset as the new default preset by adjusting the defaultPreset global settings. That way, you always have the default SPADS preset as reference in your configuration, without having to duplicate any unneeded setting declaration.