Status of VASSAL 3.2

Hello,

I am just checking on the status of VASSAL 3.2. There were two planned features that I was hoping to see implemented in that version: terrain encoding and exposing the module properties to a scripting or regular expression language. Are these still slated for version 3.2 and, if not, what are we likely to see in Version 3.2?

Thanks in advance.

Thus spake tangentRW:

Hello,

I am just checking on the status of VASSAL 3.2. There were two planned
features that I was hoping to see implemented in that version: terrain
encoding and exposing the module properties to a scripting or regular
expression language. Are these still slated for version 3.2 and, if not,
what are we likely to see in Version 3.2?

Presently, all of my attention is directed at VASSAL 4 planning. My
intention is to wrap up 3.2 while the dust settles around the 4.0
planning documents, in order to give us some time to mull them over
before we start coding seriously.

Because it’s looking like VASSAL 4 will be a completely different
codebase, I don’t want to put much further effort into the 3.2 branch
beyond what’s needed to get a functioning release. Whether either of
the features you mention appear in 3.2 depends on how near they are
to being done right now; I haven’t checked on the state of either one
in a while, so I won’t be able to answer your question until the next
time I’m working on 3.2, which might be a few weeks from now.


J.