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

feat: Use Steam API to detect Query and game ports #484

Open
dgibbs64 opened this issue Jan 17, 2024 · 4 comments
Open

feat: Use Steam API to detect Query and game ports #484

dgibbs64 opened this issue Jan 17, 2024 · 4 comments

Comments

@dgibbs64
Copy link
Contributor

dgibbs64 commented Jan 17, 2024

What is this feature about?
It is possible to use the steam API to get info about game and query ports. This could allow valve queries to check and confirm the query port without requiring port guessing. See below for an example. Gamedig could do a lookup against the api and match a query port then use that information to quickly and accurately query the correct port

https://api.steampowered.com/ISteamApps/GetServersAtAddress/v0001?addr=135.148.59.26

Additional context/references
Add any other context or references about the feature request here.

@guilhermewerner
Copy link
Contributor

But what if there are several servers on the same IP, which server would the query be made on.

Would this be useful if you are querying multiple servers? #444. Like searching for IP in the Steam API and querying each port returned.

@dgibbs64
Copy link
Contributor Author

when you are querying you will always be using ip:port. A lookup on the gameport is used to find a match.

@podrivo
Copy link
Contributor

podrivo commented Jan 29, 2024

This would be used only when using a port for querying?
So if you query only using an IP, skip the Steam API detection?

@dgibbs64
Copy link
Contributor Author

You would need to know at least the query or game port as an ip could have multiple game servers

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

No branches or pull requests

3 participants