I am using Memoir '44 module 10.16. When loaded in VASSAL 3.7.15 all die rolls display correctly.
When loaded in VASSAL 3.7.16 (platform doesn’t seem to matter) die rolls 1d, 2d, and 3d don’t work properly when playing online.
The piece is implemented using a prototype with 7 global properties and 7 display layers. When the user presses a die roll toolbar button it sends a global command to roll the correct number of dice. It will then
- reset the dice values (so the layers are cleared)
- roll the die (using a global command) to produce a d6 value in a global property
- copy the global property to the 1st die value
- repeat for other dice
- report on the dice rolled
For 4d, 5d, 6d and 7d the dice are rolled, displayed, reported, and they are transmitted to the other player, displayed and reported.
For 1d, 2d and 3d the dice are rolled, displayed, reported, but only locally. They are not transmitted to the other player over the network. There appears to be some randomness in this where they sometimes don’t work from A to B, but do work from B to A. In my tests now it doesn’t work in either direction. I have not been able to pin down exactly why it sometimes seems to work partially.
The global properties (DiceValue1 - DiceValue7) are set with Alt+1 - Alt+7 (set to the value of the d6 roll result in that global property), and Ctrl+0 to reset.
The trigger actions that receive the toolbar button commands use Ctrl+1 - Ctrl+7.
The global hotkey to roll the d6 and store the result is Shift+1 → Ctrl+X.
The Layer traits follow to the global properties above (DiceValue1 - DiceValue7).
The Report Actions use Alt+Ctrl+Shift+1 - Alt+Ctrl+Shift+7.
I tried to quickly replace the key command with named commands, but it did not appear to change anything to the observed behavior. There is no custom java code involved here, these are all stock VASSAL traits. I tried creating a new scenario from scratch so it couldn’t be something in the saved scenario, but same problem. I also tried the older previous module version (which in the past worked 100% for sure) in 3.7.16 and it has the same issue.