DayZ rules returns malformed modlist

[aclist]

This appears to relate to #299, with the names of mods and IDs being encoded in chunks. This gets parsed as generic UTF-8 strings and becomes malformed.

E.g., using the source server type against 205.178.177.113:2303 returns the following mod list at the top of the rules response.

I could not find any information about a discrete DayZ server protocol like the Arma 3 protocol v2, but presumably it exists.

The expected result is an array of human-readable mod names and workshop IDs.

Array
(
    [205.178.177.113:2303] => Array
        (
            [	] =>  ʚÎA]êk”Rearmed Server PackÞíl‹ ž¶—Dabs Framework69?¶m™MagicBox½tq–<ÝTactical FlavaQ·2"[µU¤Croco´s Quad
            [	] => bikeNcÍO’+ŽZStuff"˜¢g橎Terrain IslandsõE—ïŁ
SPBuilding§ãëö锌IndustrialModPackɖÜ.†‰BuildingsMegaModPackã‘Ò
            [	] => qº¨¤BuildingsModPack7p—ÁâpûeBaseBuildingPlus¶Ò¯”·ð8m
FlipTransportÅÜ-T¥žArma 2 Helicopters Remastered|£ºÝޙˆDayZ-
            [	] => Expansion-Vehiclesau¡çŠ!~DayZ-Expansion-Licensed"hUÞl‡¦DayZ-Expansion-Animations‚§žR™DayZ-Expansion-Market”:È©‘™
            [	] => DayZ-Expansion-Name-Tagsz“|\ޙˆDayZ-Expansion-CoreàˆÛåTÄûl
VPPAdminTools?,£Zü‘MagObfuscationPS”idS¦Survivalists_Fa
            [	] => cePaintskñ]_A°‘InventoryMoveSounds$ê—(©‡DayZ Editor Loaderá*OztM‰Dogtags¼*÷Œ^L‰CarCoverQžêÔbCodeLock¡7¢~é
            [	] => lBreachingchargeæÍ'kWindstrideClothing'ñ÷“(ö´v
MuchStuffPack
t°ï\Community FrameworkBBPcftoolsRootCl0udV3
Co
            [	] => deLockv3CrocoDocPublicdayz	designful	Expansion	GormirnTIHDSN	HelkhianaHunterzInclementDabItsATreeev1Jacob_Mango_V3	Josec
            [		] => itox
liquidrock	SPModdingStarlvVPP	Wardog.v3Wayward
Windstride