I think I might have had this in the wrong forum before.
I am running vassal 3.1.18 and I am trying to create an updater for my module.
I use the updater as specified by the reference manual, I select the old module (1.01 for reference) while open with my current module version (1.02) then I create the updater in it’s own folder.
Then I copy the old module (1.01) to the folder with the updater, double click the updater, nothing appears to happen.
I try to open the module in vassal, and it still shows up as 1.01
Am I doing something wrong here? or is the updater not working?
Thus spake Zackreaver:
I think I might have had this in the wrong forum before.
I am running vassal 3.1.18 and I am trying to create an updater for my
module.
I use the updater as specified by the reference manual, I select the old
module (1.01 for reference) while open with my current module version
(1.02) then I create the updater in it’s own folder.
Then I copy the old module (1.01) to the folder with the updater, double
click the updater, nothing appears to happen.
I try to open the module in vassal, and it still shows up as 1.01
Am I doing something wrong here? or is the updater not working?
The module updater has been changed significantly since 3.1.18. Are you
able to do this successfully in 3.2.6?
–
J.