Turn Counter - Feature Request

I don’t know if this is a feature request, bug, or existing functionality that is not obvious, but…

I want to configure a turn tracker that tracks months & years
Jan-Feb; Mar-Apr; May-Jun; Jul-Aug; Sep-Oct; Nov-Dec
1939; 1940; 1941;1942;1943;1944;1945

The existing functionality in 3.5.x almost lets me do what i want…
use a “list” for months and a “counter” for years

The problem is that the game doesn’t start in January, but in Sep-Oct

I want the turn tracker to start showing Sep-Oct 1939…
But if I enter the month as Sep-Oct; Nov-Dec; Jan-Feb; Mar-Apr; May-Jun; Jul-Aug
Then the turn tracker shows:
Sep-Oct 1939; Nov-Dec 1939; Jan-Feb 1939; Mar-Apr 1939; May-Jun 1939; Jul-Aug 1939
Sep-Oct 1940 etc…

So is there a way to tell the engine that you want to start NOT at the first list item, but somewhere in the middle…?

If not, I suggest this as a feature enhancement…

If you’re going to generally present the end-user with game start files (i.e., with pieces already pulled, instead of a true ‘fresh start’ from a new game), you can save the file with the turn tracker already set up for the right month and year.

That said, a ‘default’ in a turn tracker list (like the default zoom for a map), could be handy.

Good point, it may be impossible to tell which to use a “default” setting or a saved scenario setting…
I’ll just fix it with the scenario saved file…

The value of the Turn Counter is represented by a Global Property, and I believe you can directly modify that GP to change the Turn Counter. So, you should be able to set up a hidden piece that does a Set Global Property, triggered on a Startup GKC (you will also want a “flag” GP, which also gets set by the hidden piece and prevents the Turn Counter from being modified more than once, as Startup GKCs get triggered whenever the module is loaded, not just at the start of the game).

If you can’t directly modify the Turn Counter GP (actually, I suspect you can’t), you can instead trigger the “Next Turn Hotkey” you set for the Turn Counter the appropriate number of times (4) to advance from Jan-Feb to Sep-Oct (using a Trigger Action with a loop to trigger a Global Hotkey). One minor issue with this method: your Turn Counter report will trigger each time, also.

IIRC, the Turn Counter property is the one thing you can’t modify with SGPs. You can read it out for reporting purposes but not write to it.