Warning: Out Of Date Custom Code

[Michael R]

Running VASSAL 3.4.7 on a Mac with VASL 6.6.1 . This does not seem to be causing any problem for me; I am just letting our VASL gnomes know about it.

VASL version 6.6.1

• Extension 5SV v5.8.2 loaded
• Extension VASLOverlays_v2.02 v2.02 loaded
• Extension VBM v5.7 loaded
• Extension turnscrewv1_1 v1.1 loaded
• Extension 5FB v5.6 loaded
• Extension ChapterD v1.0 loaded
• Extension 5KIA v5.7 loaded
• Extension Drag-over-ext1 v0.0 loaded
• Extension chit-generator-2.0 v2.0 loaded
• Extension terrain-chart-1.2.1 v1.2.1 loaded
• Extension secret-dr-1.0 v1.0 loaded
• Extension OBA_CVP_Aids v1.0 loaded
• Extension festung-budapest-1.2 v1.2 - 8 May 2014 loaded
• Extension BFP_v431 v4.3.1 loaded
• Extension Aircraft52 v5.0 loaded
• Extension MapInv v0.0 loaded
• Extension 3d6 v1.0 loaded
• Board 39 is out of date. Updating...
• Update succeeded
• [Out Of Date Custom Code] This module contains outdated custom code, which is not guaranteed to work with versions of VASSAL released after 6-Aug-2021.
• [Out Of Date Custom Code] Please check whether there is an updated version of this module. If not, please contact the maintainer of this module and request that it be fixed, or post a message on the Vassal forums and ask for help.
• Using board(s): 00(v6.0) 37(v6.0) 39(v6.2)
• Saving game ...
• Game Saved

 

[A_T_Great]

That's just caused by using files saved, or created with an older version of VASL.

 

[von Marwitz]

I had such messages, too, and I believe that A_T_Great has it right.

What would interest me is what custom code could be meant by this message:

Is this something that is 'created' by the user, i.e. some HTML code entered into a draggable overlay?
Or is this something that is 'inherent' to older counters and/or extensions which cannot be influenced by the user?

Background to this question:
I would like to fathom, if pre-made VASL setups might not work any more from the given day onwards and if the end-user could 'fix' this or not.

von Marwitz

 

[uckelman]

Look in the errorLog for more details.