-
Notifications
You must be signed in to change notification settings - Fork 146
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
bug: Squad now using EOS instead of Valve #545
Comments
Side node: Satisfactory is also using EOS. If squad gets up and running I can raise an issue for it as well |
Other EOS protocols use data extracted from game files:
If someone provide these Squad credentials, I can update the implementation. (: |
It seems Squad v6 is using Valve's protocol, but Squad v7 is using EOS. Not sure how to proceed with the same game having 2 protocols depending on the version. —
|
We should always prefer the newer version, meaning that we should default it to EOS and provide another game entry for the 'older' version (that eventually will be removed). |
Hi there any news about squad servers? or can i offer some help? |
I'm not sure this is working, this is from squad's official editor clientId = |
I believe its due to the fact the Squad Game Client details require player authentication. The Squad Dedicated Server clientId/secret is different but doesnt have the required permissions on the API to query for servers, |
Describe the bug
It appears that Squad is now using EOS for server management and valve protocol appears to no longer be working. I dont have much experiance in the EOS system yet so unsure how to test it currently.
The text was updated successfully, but these errors were encountered: