Ahh… I see the problem, you must be using Vassal 3.1.18 (or 19 or 20), correct?
This appears to be another unexpected obscure side effect - the first one being the mysteriously masked headlines which forced immediate release of 1.2b - of the workaround I introduced to support independent language choice. For that to work Vassal 3.2.0 beta 3 is needed, but I still wanted to support the existing Vassal 3.1.18+ user base. I guess the workaround was too much of a dirty trick and problems are popping up.
I am sorry about it. While I think about what to do… could you please download and play with Vassal 3.2.0 beta 3, which you can find here.
Thanks for you report!