Hi!
I realize that you said that this library will not be maintained anymore, but just to let you know, valve will be implementing an (optional for now) challenge for A2S_INFO.
The feature is currently being tested and details can be found here: https://steamcommunity.com/discussions/forum/14/2974028351344359625/
Since this is a change that will completely break the current library the moment the challenge becomes mandatory, it would be nice if you could implement this as a last change and push it to pypi as well so that the library could still be used in the future without the need to rewrite old software that relies on it.
The TL;DR is that the first A2S_INFO request stays the same and if the response contains a challenge, you simply append it to the request and resend. In other words, it works just like with A2S_PLAYER but instead of passing 0xffffffff, you just send nothing, the first time.
Hi!
I realize that you said that this library will not be maintained anymore, but just to let you know, valve will be implementing an (optional for now) challenge for A2S_INFO.
The feature is currently being tested and details can be found here: https://steamcommunity.com/discussions/forum/14/2974028351344359625/
Since this is a change that will completely break the current library the moment the challenge becomes mandatory, it would be nice if you could implement this as a last change and push it to pypi as well so that the library could still be used in the future without the need to rewrite old software that relies on it.
The TL;DR is that the first A2S_INFO request stays the same and if the response contains a challenge, you simply append it to the request and resend. In other words, it works just like with A2S_PLAYER but instead of passing 0xffffffff, you just send nothing, the first time.