-
Notifications
You must be signed in to change notification settings - Fork 44
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] swiftplay Missing from VAL-MATCH-V1 #942
Comments
Hi - This should be available in the API on July 16. |
Hey there, sorry for the delay - There was some additional work needed and this is now expected to be available on August 14. If this changes again, I'll post an update here. |
Actually just got an update that they were able to get this added a few moments ago. Please let us know if you still have issues accessing this queue. |
Great! Works for me! |
Bug Description
swiftplay on PC is missing from the list of queues to select from
Problem Description
The queue path parameter from /val/match/v1/recent-matches/by-queue/{queue} was recently updated for console queues including console_swiftplay however we are missing the option for swiftplay on PC Valorant
Expected Result
I expect to be able to query /val/match/v1/recent-matches/by-queue/{queue} by swiftplay as the queue
Actual Result
Can't query swiftplay using /val/match/v1/recent-matches/by-queue/{queue}
Developer Impact
Either unable to get Swiftplay games via the API or we have to go through the matchlist for this information
Requires extra work and extra api calls for something that could be resolved by adding the queue to the list.
Player Impact
Due to possible complexity issues in getting Swiftplay, some apps may not include it even though it is a highly played mode.
Repro Steps
Visit /val/match/v1/recent-matches/by-queue/{queue} and try to find swiftplay in the queue parameter dropdown.
Issue Comments
Might want to leave this as instructions for any replies to your issue:
If you're also experiencing this issue please add any additional context that is useful, the developer impact to yourself, and the player impact to your users. As an example, if spectator-v4 isn't working it might affect a scouting site, but it could also affect a mobile app or site to share replays. Give the context on how this issue affects your project.
The text was updated successfully, but these errors were encountered: