Yes this is designed behaviour but I would propose to you its only
meant to be triggered in the failure case where a request with an
invalid challenge is sent, and not in place of the also documented
challenge request.
So yes it works but we shouldn't need to use it.
Regards
Steve
----- Original Message -----
From: "Kveri" <[email protected]>
true, but I don't know why valve should fix that (it's not a bug),
because it's working with A2S_PLAYER (or A2S_RULES) and it's documented
- A2S_PLAYER is not a workaround, it's just another way to go. I've been
using A2S_PLAYER with challenge value -1 to get challenge since protocol
48 update and I don't see a reason why valve should change anything,
since everyone is obtaining challenge number this way.
Anyway nice work with qstat, thanks, I've just updated it on my servers,
however I'm using gentoo and there is no new version in portage right
now, so I compiled it and replaced binary manually.
================================================
This e.mail is private and confidential between Multiplay (UK) Ltd. and the
person or entity to whom it is addressed. In the event of misdirection, the
recipient is prohibited from using, copying, printing or otherwise
disseminating it or any information contained in it.
In the event of misdirection, illegible or incomplete transmission please
telephone +44 845 868 1337
or return the E.mail to [email protected].
_______________________________________________
To unsubscribe, edit your list preferences, or view the list archives, please
visit:
http://list.valvesoftware.com/mailman/listinfo/hlds_linux
