[game.cfg] what is {themes}, and are all includes exclusive?

[Ethan]

Hello,
I looked into the game.cfg and I saw {themes}, this does mean include all *.cfg from the "themes" directory? If so has the targeted directory some specification? ie does this command work fine even there is a file wich is not a *.cfg?

About the file included in the game.cfg, may they be included/read somewhere else ?
About the keytool part : would it not be more readable by creating a keytool.cfg ?

And about it content, the content between APPLE and notAPPLE is that the ctr attribute is used instead cmd... May it not be changed in order to avoid (useless) content repetition ?

When is this file loaded/used ? I don't quite understand the use of the "#ifdef TUTORIAL" here...

Thanks

[Noyga]

Hello,
I looked into the game.cfg and I saw {themes}, this does mean include all *.cfg from the "themes" directory? If so has the targeted directory some specification? ie does this command work fine even there is a file wich is not a *.cfg?

It does load all *.cfg (and only .cfgs) from the themes directory

[toms]

Was it sure not {./themes} ?

And #ifdef TUTORIAL is the same as #ifdef CAMAIGN_SOMETHING, and loads the tutorial when it is selected.

The keytools.cfg is IMO a nice idea and could be done, yes.

[Ethan]

The keytools.cfg is IMO a nice idea and could be done, yes.

Already done in 1.2 infact.
But there is a new think a don't understand

[+units]
{tutorial/units}
[/units]
{tutorial/units}

I don't understand why there is two {tutorial/units}...The units tag must new I guess and the older one was not removed to not break down the game if the parser hasn't been updated ? (I can't read perl :$ )