I’m sure the issue’s a bit different than that, but that’s what I’ve got at the moment.
I’ve been going crazy trying to get a new module, with some fancy footwork, to properly report delete actions. I just noticed that an old module, where it worked, now has the same problem…
The Federation & Empire module (available through a link provided on the module page in the wiki) reports most actions taken. When deleting a unit, it reports something like “* DN deleted in 0902”. In 3.2.13 this turns into “* DN deleted in”, with the location missing. Other reports, such as creation, moving and cloning work fine.
Going through my personal collection of Vassal installers shows this cropped up between 3.2.6 (where it works) and 3.2.7 (where it doesn’t).
This appears to still be a problem for me. Even with 3.2.13. $location$ is always blank for a delete report action which I assume is the expected result. However $oldLocation$ is wrong. By that I mean. If the piece has never moved it’s blank. Otherwise oldLocation reports the location previous to where it was deleted from.
I’ll post what I’m seeing here (this is an existing module written by others that I have been modifying).
I just did some fiddling around, and I can’t find any variable that will cause proper reporting on delete. Everything else is fine, like reporting a clone, or even having that variable display in a text label. But a delete action reports one step behind.
I’m not working on VASSAL at all until we’ve moved to our new house.
(End of January?) I’ll have a look at the test case then, but if the
solution turns out to be complicated, be prepared for me to say that
I won’t work on a fix for it in 3.2. I intend to spend all of my
development time in the new year on VASSAL 4.