You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Traceback (most recent call last):
File "/Users/sergejsorohov/Documents/trash/A2S_INFO-checker/src/test.py", line 7, in <module>
print(a2s.rules(address), "\n===================")
File "/usr/local/lib/python3.9/site-packages/a2s/rules.py", line 15, in rules
return request_sync(address, timeout, encoding, RulesProtocol)
File "/usr/local/lib/python3.9/site-packages/a2s/a2s_sync.py", line 22, in request_sync
response = request_sync_impl(conn, encoding, a2s_proto)
File "/usr/local/lib/python3.9/site-packages/a2s/a2s_sync.py", line 43, in request_sync_impl
return request_sync_impl(
File "/usr/local/lib/python3.9/site-packages/a2s/a2s_sync.py", line 28, in request_sync_impl
resp_data = conn.request(a2s_proto.serialize_request(challenge))
File "/usr/local/lib/python3.9/site-packages/a2s/a2s_sync.py", line 92, in request
return self.recv()
File "/usr/local/lib/python3.9/site-packages/a2s/a2s_sync.py", line 76, in recv
packet = self._socket.recv(4096)
socket.timeout: timed out
I looked into this and found out the server uses the Goldsource multipacket format, which is not currently implemented. It's also impossible to detect on a per server basis just from the response, so supporting it would require a major API change. I consider this a valid bug, but I don't know if or when I will fix it because it's such a big change.
Why rules not work?
Invalid response type: 0x6d
orWhen i increase timeout - server not respond.
But all data from rules has been succefully parsed by every 3rd service
https://www.gametracker.com/server_info/51.38.60.53:27015/server_variables/
The text was updated successfully, but these errors were encountered: