Settings - global or particular?

[GraniteStater]

I asked this in AACW, but was never fully satisfied with the feedback. I posted this in TechSpprt, also.

Thread title says it.

* Suppose I start a game and arrive at a certain set of settings - call it SettingGroup A (SG_A). Then I save it and start a new game, with a different set of Settings - call it SG-B. When I save this and exit from it, and then, load the first game with SG_A, does the app 'remember' and apply SG_A to the reloaded game, or, is whatever the last settings are applied to the reload?

IOW, do I have to write down my Options and apply them for each instance (if global), or are the settings/Options retained and applied for each instance?

I assume one cannot change settings in-game.

[minipol]

It's a good question I've wondered about as well.

[Pocus]

Most options are one the contrary checked on the fly when used, this has pros and cons. A few special cases are there though, like random generals. If a general's stats have been randomized, removing the option will probably not revert them back. But for the rest (attrition, activation rule, off map box warfare, foreign entry) that's dynamic.

[GraniteStater]

I'm sorry, Pocus, I believe I get the import of your remarks, but could you please clarify?

I'm under the impression that Yes, you must set the Options for what you want (at least check them) for each time you start. IOW, if I'm playing a game as the Union with one set of Options, then, if I load a CSA game started with another set, then I have to select and specify the Options each and every time I load or start a game.

[minipol]

If that is so, wouldn't it be handy if we could save / load a set of options.
You could then export the options for PBEM plays too and maybe make sure that the options are linked to a PBEM save game.
This would solve another problem posted here on people saying that they weren't sure their PBEM opponents used the same settings.

[Pocus]

Yes Granite, that's how it works. For PBEM people, I know this can be tricky, on the other hand, many people only play single players and like to change on the fly some rules.

[GraniteStater]

What do you mean by 'on the fly', exactly? AFAIK, I can't change settings when the Game UI (map) is up. I have to back out of that instance and reselect my desired Options, which is tantamount to what I'm saying, if I have it correctly.

I truly do not understand why a settings.ini (or equivalent) cannot be included with each instance. However, perhaps we should resume this in TechSpprt in the thread I started, or, you can PM me, Pocus, if you feel a techy discussion may be beyond the bounds of the forums.

[Pocus]

by on the fly I mean when a game is ongoing. Not on the fly as 'I can do it from the main map'. For example you can play with standard activation during a turn, then when the new turn is up, you can decide you would prefer to play with hardened activation where the leaders are locked if not active. This is what I mean by 'on the fly', this can be done within a game, not just at game start. As I said, this is potentially a problem if you have several ongoing PBEM (then you probably be better duplicate the game folder itself), but for single players, that's generally seen as a plus.

[GraniteStater]

you can play with standard activation during a turn, then when the new turn is up, you can decide you would prefer to play with hardened activation where the leaders are locked if not active. This is what I mean by 'on the fly', this can be done within a game, not just at game start.

I think you & I are understanding the same, but differ in expressing it to a small degree. Per italics: AFAICS, I cannot alter Options/Settings/Whatever while the map is up, i. e., a particular game instance is running. However, one can back out of Instance_001 and reset the options & resume Instance_001.

Which is OK and I think I see the convenience for some, but...

in any case, I don't think yer gonna revamp fer lil' ole me.

So it's kind of a moot point, no matter how sterling my view may be. Thanks for the discussion, O Long-nosed One.