RTS Configuration Elements

posted on February 6th, 2015, 1:46 am

I have a question regarding the commands listed in the guide. As an example:

Hardcoded Configuration Commands

This section consists of commands that are hardcoded, but can be made configurable if so desired.

cfg_ATTACK_ATTACK_WAIT_TIME
Float, A2 Hardcoded Default: 7.0

Anmerkungen: scheint ganz klar etwas mit angriffen zu tun zu haben, direkt wohl wie flotten angreifen oder soetwas

cfg_ATTACK_CLOSE_ATTACK_DISTANCE
Float, A2 Hardcoded Default: 300.0

Anmerkungen: das hat etwas mit der bewegung während eines angriffes zu tun

Are these just available commands that were never added to the game? Seems like lots of neat things to get the AI to play even better/be more difficult. Did the team ever do any in depth testing or perhaps Optec?

posted on February 6th, 2015, 3:29 am

They are hardcoded to the given values - non-configurable commands. However, because they are exposed, we could have made them configurable if there had been demand.

All we knew is right there: no secrets .

posted on February 6th, 2015, 4:08 am

I appreciate the info. I guess when I saw all those commands I had visions of a better AI. Yes I know it's still rather inept no matter what, but one could dream.

And just so I understand those commands are buried in the code and usable, but the devs just never put them in the RTS_CFG?

posted on February 6th, 2015, 4:17 am

The commands are distinct elements which can take on values, but the values are hardcoded - not accessible after the code was compiled. Because the functionality is there (and a flag doesn't have to be built), they can be exposed by a skilled programmar and made to be configurable.

posted on February 6th, 2015, 4:20 am

Gotcha. So they can't just be put in the RTS_CFG now and used because they aren't exposed? Now I have to learn programming too

With everything you guys know and have done with FO I can barely fathom what FO: NX is going to be like

posted on February 16th, 2015, 2:02 am

I have another question Dominus. Per the guide we have int, float, #define which are used as inputting commands in the RTS_CFG and the strategic_AI_cfg and the AIP files for the AI.

However, we also have "double" in front of some of the commands and I was wondering what that means as a command like "double resource_dilithium_tendency = 1.0;" Is it doubling the tendency in this case or is it just a simple means of heading the command and I'm thinking to hard about it.

Also, the guide has this:

Integer Any integer. Configuration files use C++ and thus integers may serve as booleans.
Float Dot (.) is decimal separator. "Percents" are inputted as fractions.

I'm wondering if all the entries for the AI like "double resource_dilithium_tendency = 1.0;" should have had "float" in front of them? I guess those tendencies all work as is though? It just seems strange that almost all entries have float or int except the ones that use double.

posted on February 16th, 2015, 2:19 am

It's all C++ ; a double is a floating point calculation with a different precision.