I had a game file stored and subsequently edited the module for it. When next I loaded that game file I got a message like this:
“Save game was saved using module . Are you sure you want to load it using ?”
I clicked Yes, it opened fine, and I moved some units and saved the game.
But I still get that warning message every single time I load the saved game - even if I save it as a different filename. Why is this happening and can I put an end to it? BTW in this case, the modulename was actually unchanged - could that be the issue? The Module version was changed.
Thanks.
Thus spake wifferboy:
I had a game file stored and subsequently edited the module for it. When
next I loaded that game file I got a message like this:
“Save game was saved using module . Are you
sure you want to load it using ?”
I clicked Yes, it opened fine, and I moved some units and saved the
game.
But I still get that warning message every single time I load the
saved game - even if I save it as a different filename. Why is this
happening and can I put an end to it? BTW in this case, the modulename
was actually unchanged - could that be the issue? The Module version
was changed.
What module? Can you post the save here so we can see it?
–
J.
It is not yet for public release. I will have to PM it to you, but am waiting to hear back from the rights-holder for permission.
I sent you a PM this morning but it’s been in the Outbox for 12 hours.
Is there something wrong with the server?
Thus spake wifferboy:
I sent you a PM this AM but it’s been in the Outbox for 12 hours.
Is there something wrong with the server?
I was doing some maintenance on the machine that hosts our VMs on
Sunday morning.
–
J.
Now I have two PMs to you that will not leave the Outbox and cannot be deleted.
But it looks like one of the messages from Sunday morning made it to you now.
Thus spake wifferboy:
Now I have two PMs to you that will not leave the Outbox and cannot be
deleted.
That’s strange. I’ll look into it when I’m home again on Friday.
–
J.
I found the problem with the warning message. I had inadvertently added a space following the module name, so it looked like a different module to Vassal but not to me. 
But in the PM that was sent to you I describe another problem with SHIFT M not working in a “Send To” command. Could you please take a look at that? Thank you.
Thus spake wifferboy:
Now I have two PMs to you that will not leave the Outbox and cannot be
deleted.
I think I received both. Can you delete them now?
–
J.
They are all now finally in the Sent folder.
Thus spake wifferboy:
But in the PM that was sent to you I describe another problem with SHIFT
M not working in a “Send To” command. Could you please take a look at
that? Thank you.
I see this problem in your module, but not the cause. I need you to
reproduce the problem in a minimal test module.
–
J.
I’m sorry. What do you mean by a “minimal test module”? What should be in it?
Thus spake wifferboy:
I’m sorry. What do you mean by a “minimal test module”?
I mean a module that contains nothing which isn’t necessary for
demonstrating the problem. If you can remove an item from a module,
but the problem persist after removing it, then that item wasn’t
necessary for demonstrating the problem.
–
J.
In trying to make the minimal module, I found the problem. Each “Send To” also has a “Send Back” and in one instance for a different map, the Send Back command was a typo. Instead of SHIFT B, it was SHIFT M. When I removed that Send To command, the one needing SHIFT M to work for the Send To then functioned correctly.
I had looked at all the Send To commands and others like the Mark Moved (of which I was initially suspicious). I had examined all those until I was cross-eyed, but it had never occurred to me to look at the Send Back sub-commands.
I suspect you thought this would happen when I started deleting stuff to get to a “minimal module” and of course when I tested for the problem, it had gone! Then by process of elimination, I found the problem trait.
Thanks very much for your help.
Thus spake wifferboy:
In trying to make the minimal module, I found the problem. Each “Send
To” also has a “Send Back” and in one instance for a different map, the
Send Back command was a typo. Instead of SHIFT B, it was SHIFT M. When I
removed that Send To command, the one needing SHIFT M to work for the
Send To then functioned correctly.
I suspect you thought this would happen when I started deleting stuff to
get to a “minimal module” and of course when I tested for the problem,
it had gone! Then by process of elimination, I found the problem trait.
After I checked that the keystroke was getting through, I started to
suspect that it was a module bug, yes. Eliminating parts until the
problem disappears is a good way to find problems like this.
–
J.