Skip to content

Conversation

@jaduplansti
Copy link
Contributor

@jaduplansti jaduplansti commented Nov 15, 2025

Added #13 (RIOT)

I had to do some digging, but i made it work.

@kaifcodec
Copy link
Owner

Hey, @jaduplansti this one literally looks like it have valorant's private API usage and the work you have done might be challenging, really appreciable work.

  • But did you test it locally with every cases?
  • Did it work well without rate limits or anything?

@jaduplansti
Copy link
Contributor Author

Yep i have tried it locally.

  1. i tested with a invalid username, private username and a available username.

  2. yes there are no rate limits as far as i know.

@kaifcodec
Copy link
Owner

@jaduplansti Thanks for the update! I tested it myself, and the code looks solid. I plan to merge it after I add a small tweak: skipping Valorant checks for plain usernames and prompting the user at the end to optionally run a separate check with the proper Name#Tag format.

The reason is that Valorant usernames use a “Name#Tag” format. Right now, if someone enters just a plain username like alex, the API returns “NotFound,” which the script interprets as Available!, this can be misleading since common usernames usually exist with some tag.

If you want, you could also implement this logic in __main__.py and update the PR, then I can merge it immediately without waiting. Either way, really appreciate your work on this!

@kaifcodec kaifcodec added the need-extra-changes Some files or parts of the code may require additional edits or updates for it work properly. label Nov 16, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

need-extra-changes Some files or parts of the code may require additional edits or updates for it work properly.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants