v3.6.0(pre-release) - error when joining from Vassal 3.5.5

Technical Support & Bugs
1

When I started an online game using VASSAL-3.6.0-SNAPSHOT-3fc19a0-macos and then joined it from the same module using Vassal v3.5.5, I received the following error message in the v3.5.5 immediately on joining. The game itself seemed unaffected. The exact same module, saved under v3.5.5, was used in both cases.

  • Waiting for Game Info…
  • Synchronization complete
  • Bad Data in Module: Unknown type nonRect2;1.0;m,0,-37,l,0,-36,l,-2,-36,l,-2,-35,l,-4,-35,l,-4,-34,l,-5,-34,l,-5,-33,l,-7,-33,l,-7,-32,l,-9,-32,l,-9,-31,l,-10,-31,l,-10,-30,l,-12,-30,l,-12,-29,l,-14,-29,l,-14,-28,l,-15,-28,l,-15,-27,l,-17,-27,l,-17,-26,l,-19,-26,l,-19,-25,l,-21,-25,l,-21,-24,l,-23,-24,l,-23,-23,l,-24,-23,l,-24,-22,l,-26,-22,l,-26,-21,l,-28,-21,l,-28,-20,l,-29,-20,l,-29,-19,l,-31,-19,l,-31,-18,l,-32,-18,l,-32,-17,l,-32,-16,l,-32,-15,l,-32,-14,l,-32,-13,l,-32,-12,l,-32,-11,l,-32,-10,l,-32,-9,l,-32,-8,l,-32,-7,l,-32,-6,l,-32,-5,l,-32,-4,l,-32,-3,l,-32,-2,l,-32,-1,l,-32,0,l,-32,1,l,-32,2,l,-32,3,l,-32,4,l,-32,5,l,-32,6,l,-32,7,l,-32,8,l,-32,9,l,-32,10,l,-32,11,l,-32,12,l,-32,13,l,-32,14,l,-32,15,l,-32,16,l,-32,17,l,-32,18,l,-32,19,l,-32,20,l,-30,20,l,-30,21,l,-29,21,l,-29,22,l,-27,22,l,-27,23,l,-25,23,l,-25,24,l,-24,24,l,-24,25,l,-22,25,l,-22,26,l,-20,26,l,-20,27,l,-19,27,l,-19,28,l,-17,28,l,-17,29,l,-15,29,l,-15,30,l,-14,30,l,-14,31,l,-12,31,l,-12,32,l,-10,32,l,-10,33,l,-8,33,l,-8,34,l,-6,34,l,-6,35,l,-5,35,l,-5,36,l,-3,36,l,-3,37,l,-1,37,l,-1,38,l,2,38,l,2,37,l,4,37,l,4,36,l,6,36,l,6,35,l,7,35,l,7,34,l,9,34,l,9,33,l,11,33,l,11,32,l,13,32,l,13,31,l,14,31,l,14,30,l,16,30,l,16,29,l,18,29,l,18,28,l,19,28,l,19,27,l,21,27,l,21,26,l,23,26,l,23,25,l,24,25,l,24,24,l,26,24,l,26,23,l,28,23,l,28,22,l,29,22,l,29,21,l,31,21,l,31,20,l,33,20,l,33,19,l,33,18,l,33,17,l,33,16,l,33,15,l,33,14,l,33,13,l,33,12,l,33,11,l,33,10,l,33,9,l,33,8,l,33,7,l,33,6,l,33,5,l,33,4,l,33,3,l,33,2,l,33,1,l,33,0,l,33,-1,l,33,-2,l,33,-3,l,33,-4,l,33,-5,l,33,-6,l,33,-7,l,33,-8,l,33,-9,l,33,-10,l,33,-11,l,33,-12,l,33,-13,l,33,-14,l,33,-15,l,33,-16,l,33,-17,l,33,-18,l,33,-19,l,31,-19,l,31,-20,l,29,-20,l,29,-21,l,28,-21,l,28,-22,l,26,-22,l,26,-23,l,24,-23,l,24,-24,l,22,-24,l,22,-25,l,21,-25,l,21,-26,l,19,-26,l,19,-27,l,17,-27,l,17,-28,l,15,-28,l,15,-29,l,14,-29,l,14,-30,l,12,-30,l,12,-31,l,10,-31,l,10,-32,l,9,-32,l,9,-33,l,7,-33,l,7,-34,l,5,-34,l,5,-35,l,3,-35,l,3,-36,l,2,-36,l,2,-37,c
    not found in BasicCommandEncoder’s list of traits and basic pieces.

Examining the v3.5.5 Vassal log, I find many more such messages. Also, at both ends I see a string of bsh. messages logged, starting with an “bsh.InterpreterError: Unimplemented binary String operator”.

Both log files attached.

2

Hi Mark – we’ll probably need a copy of the version of your module that did that. Brian

3

Yes, the InterpreterError is something different form nonRect2 errors. Looks ike you’ve fixed the Rect2 one, I’ll put in a separate report and link to module for the other one.

4

Hi Mark,

I am already working on improving the error report for the Interpreter error as part of bug 13401. It should be generating a Bad Data Error, not a crash and I will add some of the extra info in the log file that I mentioned in 13401.

The actual cause of the error is a Layer follow level expression that is attempting to do some sort of arithmetic or comparison between a String and a non-String. There may be a further underlying bug, but the improved reporting should help track that down.

Brent.