Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update in A2S_INFO packet (added challenge) #85

Open
overfl0 opened this issue Jan 19, 2021 · 2 comments
Open

Update in A2S_INFO packet (added challenge) #85

overfl0 opened this issue Jan 19, 2021 · 2 comments

Comments

@overfl0
Copy link
Contributor

overfl0 commented Jan 19, 2021

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.

@overfl0
Copy link
Contributor Author

overfl0 commented Jan 19, 2021

Also, at the end of the first page of the steam discussion, there is someone who posted their server IP and port for testing

@Yepoleb
Copy link
Member

Yepoleb commented Jan 20, 2021

The challenge is already implemented in python-a2s. I have no interest in doing double the work for a few people who can't be bothered to update a few lines of their code. Also nobody apart from the owner has access to the official PyPi package, so it would have to be published under a new name, requiring old software to be manually patched anyway.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants