This seventh part shows how to override config values.
It also shows how to use debug and release versions on different data sets or, on the contrary, on the same one.

We can specify as many config files we want using the command line (-c / --config switch).

The config file list can also be provided through the main config file (the one that has same base name as the executable) in the [Param] section with the 'config' key.

In the same order of idea, all command line parameters can be specified in the [Param] section, using the command switch long name (plugin for -p / --plugin, config for -c / --config, etc...).

The config inheritance system (using the '@' marker) combined with the config override process allows easy parameter tweaking and linking for various build configurations, or even for multiple game prototyping.
Separating your config into multiple files can also be very helpful.

You can also modify any config value loaded in memory, add new ones and save all of them in a file for further use or manual tweaking.

As orx is data-driven, with the same code you can have very different behaviors depending on which config set you decide to load.

Config files can also be reloaded at runtime, provided you asked to keep track of the load chronology. This is done in the [config] section, using the 'History' key.

This tutorial is almost done, in the last part we'll just show our different results based on the same code with different config sets.

---

For more info, please see orx-project.org

Tutorial files (including executable) can be found here: orx-project.org/orx/orx-test-video.zip