I'm specifically using the "e" query/batch server list query. I've setup some basic checks like make sure length is at least 16bytes(header info + at least 1 ip/port combo), length must be even, not including the length of the header info, the rest of the ip/port data length must be evenly divisible by 6, and also that the header info is what it should be. But I'm noticing instances like I get sent a runt packet of 22 bytes. This packet meets all the above criteria, but it's the very first packet or maybe a few down in the sequence.
If your 'runt' packet doesn't begin with...
0xFF, 0xFF, 0xFF, 0xFF, 'f'
...then should should bail out (and possibly restart the transfer from the beginning?).
Are the bytes in the broken packet consistent (same thing each time you try it) or do you get random garbage each time. If it's consistent, what are the 22 bytes that you are getting?
-- Jeffrey "botman" Broome
_______________________________________________ hlds_apps mailing list [EMAIL PROTECTED] http://list.valvesoftware.com/mailman/listinfo/hlds_apps
