The remaining configuration options don’t have dedicated screens like the ones we’ve seen so far. Changing them requires that we edit the game’s configuration files.
Table of Contents
To edit the configuration files:
Coders can also click on the “Advanced Editor” button to edit the raw config file.
Ares config files use YAML, a simple formatting language. Here’s a little overview that should be enough to get you started. You can refer back to this page as you go through the remaining steps of this tutorial and learn how to set various config options.
Many config options are just strings, so you can edit them just by putting a value into the edit box. For example:
Number values are similar.
Some config options are lists. List the values, one per line, with a hyphen in front of each line.
[]
. Do not just leave the text blank or your game will probably have errors.
The most complex config options are multi-field data structures called hashes.
The simplest hashes are just name/value pairs, like this one listing demographic names and their corresponding command syntax:
But many hashes have more complex, nested data, like this group config:
Here we have a name/value pair like Faction:FactionData
, but note that FactionData is itself a hash with name/value pairs like desc:Description
and value:FactionChoices
.
Hashes can be tricky to edit. Make sure your indentation lines up and you have values for all required fields.
{}
. Do not just leave it empty or your game will probably have errors.
The tips above should be enough to get you started, but when you’re ready you can see the Understanding YAML tutorial for more details and troubleshooting help.