Minor quibble....

[Jazz]

When I log onto the server running VASSAL 3.6.6/VASL 6.6.3.1, I get what look like a number of raw HTML formatting symbols. Does not seem to affect functionality in any way that I could see.

Not seeing them when logging into the room for other VASSAL modules.

As advertised, a minor quibble.

 

[Michael R]

I see this also with 3.6.2 and 6.6.3

 

[PezBailarin]

with other vassal modules you see the same texts when you join the server, it's just the html is properly parsed. For example this is Up Front module:

 

[Jazz]

with other vassal modules you see the same texts when you join the server, it's just the html is properly parsed. For example this is Up Front module:

View attachment 20130

That much is obvious?

The pertinent question is why is the html formatting is not properly parsed?

 

[Michael R]

I remember hearing that VASL or VASSAL had a limited ability to interpret HTML in the labels on counters. Perhaps it is VASL?

 

[von Marwitz]

I remember hearing that VASL or VASSAL had a limited ability to interpret HTML in the labels on counters.

This part is correct for sure.
I do not know, though, if it is related to the problem.

von Marwitz

 

[Jazz]

Never thought of that. Come to think, the previous welcome message only had straight text with no need for html formatting?

 

[Michael R]

I don’t remember any welcome message in 3.5.8 or earlier, but I might not have noticed.

 

[zgrose]

my 100% guess: the custom "chatter" functionality in VASL is the point of failure

 

[Jazz]

I don’t remember any welcome message in 3.5.8 or earlier, but I might not have noticed.

A single short line of text that informed the server was being entered. Easily overlooked.

 

[von Marwitz]

my 100% guess: the custom "chatter" functionality in VASL is the point of failure

Do you think that the Extension, which is obsolete, is the cause of trouble or that same functionality which has become an inherent part of VASL?



I seem to recall that still using the Extension was causing some troubles. If so, deleting the Extension would be a quick and easy fix.

von Marwitz

 

[zgrose]

the extension was rolled into the base module. my guess is that those classes need to be updated to accommodate the server now sending formatted text.

 

[Jazz]

Do you think that the Extension, which is obsolete, is the cause of trouble or that same functionality which has become an inherent part of VASL?

View attachment 20163

I seem to recall that still using the Extension was causing some troubles. If so, deleting the Extension would be a quick and easy fix.

von Marwitz

Data point: I do not have the chatter extension in my extensions folder.

 

[zgrose]

Issue/change confirmed. VASSAL now uses its own formatting codes for system messages that the VASL custom message parser does not understand at the moment.

 

[DougRim]

Issue/change confirmed. VASSAL now uses its own formatting codes for system messages that the VASL custom message parser does not understand at the moment.

I have created an issue on Github.