> Rodney, is there something we could do to make this update automatically?
Not really. The component changed some when it was added to the core engine, so the buildFile won't be compatible. It would be nice to catch these errors and give the user an error message that suggests switching to the exact same VASSAL version as the module was built using. The current version check assumes that later-numbered versions will be backward-compatible, which isn't always the case when custom code is involved. rk [Non-text portions of this message have been removed]
