I have two versions of a module Europa_Balkan_Front and the code for the Europa Turn [Turn Counter] looks to be the same.
In version 0.90.0 the counter only advances the first level (years). The months and fortnights can only be set manually.
In version 0.90.1 the counter works as I intend, with fortnights, then months, then years.
Is this a recognized bug?
Daniel
When I press the + button on the turn interface, I see
* * <a> Turn Updated from 1940 Nov I to 1940 Nov II
* * <a> Turn Updated from 1940 Nov II to 1940 Dec I
* * <a> Turn Updated from 1940 Dec I to 1940 Dec II
* * <a> Turn Updated from 1940 Dec II to 1941 Jan I
* * <a> Turn Updated from 1941 Jan I to 1941 Jan II
* * <a> Turn Updated from 1941 Jan II to 1941 Feb I
* * <a> Turn Updated from 1941 Feb I to 1941 Feb II
Isn’t that what you expect?
In my module Anzio Beachhead I similarly have a three level turn counter
Maybe that can help if the above isn’t what you expect.
BTW, it seems like you have duplicate accounts @Daniel_T_Shaw, @Daniel_T_Shaw, and @Daniel_T_Shaw - perhaps you can get @uckelman to merge them for you. You just need to let Joel know which one you want to merge into.
Yours,
Christian
Even more mysterious. I just tried again with version 0.90.0
The filename is Balkan_Front_Second_Edition_(BF2)_GRD_2002_v0_90.vmod
I used the Blank Map setup (but I believe the problem applies to all the preloaded setups).
My turn counter advances in years and the log says
* * Turn Updated from 1939 Sep I to 1940 Sep I
* * Turn Updated from 1940 Sep I to 1941 Sep I
If it would do as your log, I’d be very happy.
Another user complained to me of the same result, which is why I made version 0.90.1
The difference between the versions is the predefined setup files. In version 0.90.0 I used the same files I used in version 0.80.0
0.90.1 has setups created by opening the old vsav files, selecting all the counters, log, clone, end log and with a new empty map (not the blank map vsav) load continuation with that same vlog.
Daniel
PS I will talk to uckleman again about my aliases. Your message above appeared in all my email accounts, so maybe I’m ok with multiple aliases.
If your goal is create new predefined setups that fully incorporate all changes to a module, this procedure is extremely unlikely to work–and I’m pretty tempted to say it’s certain to not work. You should be recreating setups from scratch or using the Editor’s “Refresh Predefined Setups” feature.
Ok, so my approach to creating my setups might be unorthodox. So far, it has worked for me.
That doesn’t answer why some users are not seeing the date advance correctly in version 0.90.0 with what looks like the same code as version 0.90.1
Furthermore, I tried using the “Refresh Predefined Setups” tool, saved to a different file name, and still the year advances before the fortnight. So that did not solve the issue.
The module in question was uploaded with Vassal 3.7.19 and the issue was found with that version running. I’m now running Vassal version 3.7.20 and that seems to make no difference.
My version 0.90.1 is working fine. I’m only raising this so others, particularly those using the “Refresh Predefined Setups” tool, don’t drop into the same (or similar) issues.
Now my suspicions (which might be wrong, because I’m an amateur user). My previous setups did have a simple one level default variable “Turn” with an ordered list of values. When I rebuilt the turn tracker to use three levels (Year, Month, Fortnight) then with the old setups the years advance oddly. As I said, the “Refresh Predefined Setups” tool does not fix this problem. I think the “Refresh Predefined Setups” tool only deals with changes to the piece definitions, not changes to the use of variable names.
Now, I’m glad I have my unorthodox method of getting pieces from one version of my module to a redesigned version of the same game. Otherwise, you’d be having me recreate dozens of pieces from scratch.
Daniel
I think your suspicion is correct: Vassal stores the Turn Counter state in the save files. If that does not get updated correctly on Refresh Predefined Setups. When the save is then read, the Turn Counter is then decoded to only have one level, and so switching to the next turn only changes that level.
There is a way, using pywargame - shameless self-plug 
- to write a setup from a spreadsheet. It is by all means not fool proof, but can minimize the need for the pesky Refresh Predefined Setups.
BTW, my result above was based on your version 0.9.1.
It can be a bit confusing to users to have multiple accounts - who to write to? So great that you got them merged.
Yours,
Christian