First, everything changed in this update is additive. This update will not make any of your old configs break or anything, this just adds a new way to work with more configs.
********
Changes:
Now you can make a rtpSettings file take values from another file. The general idea of this is that if you want two rtpSettings where the only difference is the [any-option-what-at-all], you can make the second rtpSettings file super easily.

How To Use
If you want another settings file to inherit all unset settings from another file,
simply add a line that says `load-from: [settings-name]` to it. In the new file, you can include as many or as few options as you would like. For any options you do not include, the value will be taken from the settings defined in `load-for`, but any setting you include will take effect.

Example
For this explanation, lets assume that you still have an rtpSettings file named `default-settings.yml` and that this settings file is properly configured.

Now lets say that you want to make another rtpSettings file where everything is identical to `default-settings.yml`, except the cool-down is 555 seconds and the then-execute command contains a lot of "Q"s. To do this, all you would need to do is make a new file (named whatever you would like, but for this example it will be named `testy.yml`) and make it look something like this:
So there are two lines that are required for this, the ` load-from` line and the `enabled` line. The `enabled` line is always required for an rtpSettings file to be loaded, but the `load-from` line is only used to grab values from another config. If the load-from line is present, any configurable option in the current file that is not present will get the same value as that in the named settings. So for this example, since we are loading from `default-settings`, the warm-up time, for example, of `testy` will be the same as `default-settings`.

More words
The example I made up for the last section is really a weird example to go with so here are some more.
Say you want to have 3 rtpSettings where the only difference is the distribution, all you would have to do is configure the main one, then make two more that inherit (using `load-from`) from the first, and set their distribution. With this new way of configuring, two of the files would only have to be 2 lines long, and if you ever make changes to the first one, it will carry over

Sneaky Bug Fixes
In v0.12, the message displayed when someone used `/rtp` on a settings that costed in-game money was not properly parsed. This has been fixed.