Sometimes, a user may request behaviour that, although useful for them, wouldn't be useful for others.
Ordinarily, in such instances, we would refer such a user to SG-MethodScript or coding an add-on themselves.

On occasion, such a feature may be extremely easy to implement on our end (i.e. a toggle for an existing check).
In such cases, (especially at the the request of a few users), the modified behaviour should be made available.

Having said that, given that these behaviours are used to facilitate edge cases and are thus unlikely to be widely used, including them in the main config file would confuse more users than it would help.

There are two proposed solutions to this:

advancedConfig.yml

This file would not generate automatically; a user would need to download it from somewhere, place it in their Stargate directory, and restart the server.

This file would have edge case toggles and their associated prompts.

Key distribution management for the default config.yml

Another option would simply be to exclude several setting keys from the config.yml distributed by default.
If anyone wants to add a custom flag to the config, they could be instructed to manually add a line to the effect of:
settingName: true

Implementation for this, as well as the possible contents of such a file, will be tracked via this issue.

Most of these cases have been handled within the existing framework/config.
This issue will be reopened should that change.