While i was fixing the "one packet" syndrom, i made the
socket persistent (no open/close sequence for each
command) and i've also made the challenge sequence,
for new HL servers, unique.
I don't know if it can expire, if someone knows
better...
BTW another corrolary is that we may receive a delayed
packet from a previous command now that the socket
isn't destroyed systematicaly. Call it bad luck, we're
dealing with UDP after all :)
Logged In: YES
user_id=18013
I should test my changes a bit more...
Now we get full logs on map changes...etc... :)
Logged In: YES
user_id=18013
"9No challenge for your address"
Let's fix the fix...