Malformed mods/signatures in Arma 3 listing
I've got an Arma 3 server with an entry on battlemetrics whose mods and signatures have appeared corrupted for some amount of time, and I believe it has to do with how it parses A2S_RULES from Arma 3. Battlemetrics used to render our mods and signatures correctly, but I suspect some change to our modlist may have tripped up the parser.
Server link: https://www.battlemetrics.com/servers/arma3/28484414
8 Replies
This may fix itself in a few hours since I've got a few mod changes planned, specifically replacing our Expeditionary Forces and Western Sahara CDLC with equivalent compatibility mods, so I'll mention here if that works
Not sure if I'm allowed to upload this, but if anyone at BM wants to technically debug it, I've captured a datagram of the A2S_RULES response:
i also incidentally wrote my own valve source query parser which appears to handle our server's modlist correctly, so here's what the result should look like:
okay, can confirm that arma's creator DLC caused the mod list to break, as after replacing them, the mod list was fixed:
if it helps narrow down the bug in BM, this A2S output shows the CDLC are the only mods that contain 0-length names, so maybe that's what caused the BM mod list to be corrupted?
also for reference, here is the A2S_RULES response format documentation for arma:
https://community.bistudio.com/wiki/Arma_3:_ServerBrowserProtocol3
I accidentally found another issue likely related to this parser, but for DayZ instead of Arma 3:
https://www.battlemetrics.com/servers/dayz/32351316
This server's modlist is almost correct, but there are five additional "workshop mods" that are actually supposed to be signature filenames, but were misidentified as mods and given invalid workshop links:
i had to fix my own library as well and i added their payload to my test suite, so here's what it should look like:
(note that there's both a mod named AllCountryFlags and a signature file named AllcountryFlags, the one further up the mod list in BM is correct)