A Python app which retrieves the rank and players' equipped skins during a match

The application crashes when it goes from menu to in game updates.

+-------------------------------------------------------------------------------------------+
|                                 Valorant status: In-Menus                                 |
+-------+-------+---------------+-----------+----+-----------+----------------------+-------+
| Party | Agent |      Name     |    Rank   | RR | Peek rank | Leaderboard Position | Level |
+-------+-------+---------------+-----------+----+-----------+----------------------+-------+
|   ■   |       | bboychris#OCE | Diamond 2 | 38 | Diamond 3 |          0           |   82  |
+-------+-------+---------------+-----------+----+-----------+----------------------+-------+
Fetching Players [#####################################!  ] (!) 13/14 [93%] in 2.5s (5.23/s)
Traceback (most recent call last):
  File "c:\Users\BBOYCHRIS\Desktop\CODING\VALORANT-rank-yoinker\main.py", line 522, in <module>
    rank = getRank(player["Subject"], seasonID)
  File "c:\Users\BBOYCHRIS\Desktop\CODING\VALORANT-rank-yoinker\main.py", line 306, in getRank
    for season in r["QueueSkills"]["competitive"]["SeasonalInfoBySeasonID"]:
TypeError: 'NoneType' object is not iterable
PS C:\Users\BBOYCHRIS\Desktop\CODING\VALORANT-rank-yoinker> ```

[2022.05.18-22.30.19] config opened [2022.05.18-22.30.19] got cooldown with value '1' [2022.05.18-22.30.20] retrieved agent dict: {None: None, 'dade69b4-4f5a-8528-247b-219e5a1facd6': 'Fade', '5f8d3a7f-467b-97f3-062c-13acf203c006': 'Breach', 'f94c3b30-42be-e959-889c-5aa313dba261': 'Raze', '22697a3d-45bf-8dd7-4fec-84a9e28c69d7': 'Chamber', '601dbbe7-43ce-be57-2a40-4abd24953621': 'KAY/O', '6f2a04ca-43e0-be17-7f36-b3908627744d': 'Skye', '117ed9e3-49f3-6512-3ccf-0cada7e3823b': 'Cypher', '320b2a48-4d9b-a075-30f1-1f93a9b638fa': 'Sova', '1e58de9c-4950-5125-93e9-a0aee9f98746': 'Killjoy', '707eab51-4836-f488-046a-cda6bf494859': 'Viper', 'eb93336a-449b-9c1b-0a54-a891f7921d69': 'Phoenix', '41fb69c1-4189-7b37-f117-bcaf1e96f1bf': 'Astra', '9f0d8ba9-4140-b941-57d3-a7ad57c6b417': 'Brimstone', 'bb2a4828-46eb-8cd1-e765-15848195d751': 'Neon', '7f94d92c-4234-0a36-9646-3a87eb8b5c89': 'Yoru', '569fdd95-4d10-43ab-ca70-79becc718b46': 'Sage', 'a3bfb853-43b2-7238-a4f1-ad90e9e46bcc': 'Reyna', '8e253930-4c05-31dd-1b6c-968525494517': 'Omen', 'add6443a-41bd-e414-f6ad-e58d267f4e95': 'Jett'} [2022.05.18-22.30.20] VALORANT rank yoinker v1.251 [2022.05.18-22.30.20] got version from logs 'release-04.09-shipping-3-708238' [2022.05.18-22.30.20] fetch: url: 'custom', endpoint: https://shared.kr.a.pvp.net/content-service/v3/content, method: get, response code: 200 [2022.05.18-22.30.20] retrieved season id: 3e47230a-463c-a301-eb7d-67bb60357d4f [2022.05.18-22.30.20] fetch: url: 'local', endpoint: /chat/v4/presences, method: get, response code: 200 [2022.05.18-22.30.20] fethced presences: [2022.05.18-22.30.20] getting new MENUS scoreboard [2022.05.18-22.30.20] retrieved party members: [{'Subject': '110fa43c-719b-5abd-a762-300f4fb5e55f', 'PlayerIdentity': {'AccountLevel': 75}}] [2022.05.18-22.30.20] got version from logs 'release-04.09-shipping-3-708238' [2022.05.18-22.30.20] retrieved names dict: {'110fa43c-719b-5abd-a762-300f4fb5e55f': 'Alice#????'} [2022.05.18-22.30.20] got version from logs 'release-04.09-shipping-3-708238' [2022.05.18-22.30.20] fetch: url: 'pd', endpoint: /mmr/v1/players/110fa43c-719b-5abd-a762-300f4fb5e55f, method: get, response code: 200 [2022.05.18-22.30.20] retrieved rank successfully [2022.05.18-22.30.21] fetch: url: 'local', endpoint: /chat/v4/presences, method: get, response code: 200 [2022.05.18-22.30.21] fethced presences: [2022.05.18-22.30.22] fetch: url: 'local', endpoint: /chat/v4/presences, method: get, response code: 200 [2022.05.18-22.30.22] fethced presences: [2022.05.18-22.30.23] fetch: url: 'local', endpoint: /chat/v4/presences, method: get, response code: 200 [2022.05.18-22.30.23] fethced presences: [2022.05.18-22.30.24] fetch: url: 'local', endpoint: /chat/v4/presences, method: get, response code: 200 [2022.05.18-22.30.24] fethced presences: [2022.05.18-22.30.26] fetch: url: 'local', endpoint: /chat/v4/presences, method: get, response code: 200 [2022.05.18-22.30.26] fethced presences: [2022.05.18-22.30.27] fetch: url: 'local', endpoint: /chat/v4/presences, method: get, response code: 200 [2022.05.18-22.30.27] fethced presences: [2022.05.18-22.30.28] fetch: url: 'local', endpoint: /chat/v4/presences, method: get, response code: 200 [2022.05.18-22.30.28] fethced presences: [2022.05.18-22.30.29] fetch: url: 'local', endpoint: /chat/v4/presences, method: get, response code: 200 [2022.05.18-22.30.29] fethced presences: [2022.05.18-22.30.30] fetch: url: 'local', endpoint: /chat/v4/presences, method: get, response code: 200 [2022.05.18-22.30.30] fethced presences: [2022.05.18-22.30.31] fetch: url: 'local', endpoint: /chat/v4/presences, method: get, response code: 200 [2022.05.18-22.30.31] fethced presences: [2022.05.18-22.30.32] fetch: url: 'local', endpoint: /chat/v4/presences, method: get, response code: 200 [2022.05.18-22.30.32] fethced presences: [2022.05.18-22.30.33] fetch: url: 'local', endpoint: /chat/v4/presences, method: get, response code: 200 [2022.05.18-22.30.33] fethced presences: [2022.05.18-22.30.34] fetch: url: 'local', endpoint: /chat/v4/presences, method: get, response code: 200 [2022.05.18-22.30.34] fethced presences: [2022.05.18-22.30.35] fetch: url: 'local', endpoint: /chat/v4/presences, method: get, response code: 200 [2022.05.18-22.30.35] fethced presences: [2022.05.18-22.30.36] fetch: url: 'local', endpoint: /chat/v4/presences, method: get, response code: 200 [2022.05.18-22.30.36] fethced presences: [2022.05.18-22.30.37] fetch: url: 'local', endpoint: /chat/v4/presences, method: get, response code: 200 [2022.05.18-22.30.37] fethced presences: [2022.05.18-22.30.38] fetch: url: 'local', endpoint: /chat/v4/presences, method: get, response code: 200 [2022.05.18-22.30.38] fethced presences: [2022.05.18-22.30.39] fetch: url: 'local', endpoint: /chat/v4/presences, method: get, response code: 200 [2022.05.18-22.30.39] fethced presences: [2022.05.18-22.30.40] fetch: url: 'local', endpoint: /chat/v4/presences, method: get, response code: 200 [2022.05.18-22.30.40] fethced presences: [2022.05.18-22.30.41] fetch: url: 'local', endpoint: /chat/v4/presences, method: get, response code: 200 [2022.05.18-22.30.41] fethced presences: [2022.05.18-22.30.42] fetch: url: 'local', endpoint: /chat/v4/presences, method: get, response code: 200 [2022.05.18-22.30.42] fethced presences: [2022.05.18-22.30.43] fetch: url: 'local', endpoint: /chat/v4/presences, method: get, response code: 200 [2022.05.18-22.30.43] fethced presences: [2022.05.18-22.30.49] fetch: url: 'local', endpoint: /chat/v4/presences, method: get, response code: 200 [2022.05.18-22.30.49] fethced presences: [2022.05.18-22.30.50] fetch: url: 'local', endpoint: /chat/v4/presences, method: get, response code: 200 [2022.05.18-22.30.50] fethced presences: [2022.05.18-22.30.50] getting new INGAME scoreboard [2022.05.18-22.30.50] got version from logs 'release-04.09-shipping-3-708238' [2022.05.18-22.30.50] fetch: url: 'glz', endpoint: /core-game/v1/players/110fa43c-719b-5abd-a762-300f4fb5e55f, method: get, response code: 200 [2022.05.18-22.30.50] retrieved coregame match id: '273f8860-399b-4fa1-bc6b-262cc3971105' [2022.05.18-22.30.50] got version from logs 'release-04.09-shipping-3-708238' [2022.05.18-22.30.50] fetch: url: 'glz', endpoint: /core-game/v1/matches/273f8860-399b-4fa1-bc6b-262cc3971105, method: get, response code: 200

log-2.txt log-1.txt

Got this error today whilst playing comp. yoinker seems to run whilst in lobby but when I join a comp game, this error occurs. I play on Sydney, Australia servers.

Instead of exiting the program and having the user to run it again every time, It's better to keep the window open and just wait for an enter key to update the table, this seems more convenient. Note: the presence function is renamed to get_presence so that it does not collide with the local variable's name (Python complains about this)

A logging flag that could enable a write-to-file module to keep a trace of games we played and chat logs. (as it shows on the console I guess) The actual log files are more technical than details printed on our console ...

1. The preview is messed up and doesnt actually show what I changed, see https://www.diffchecker.com/rHzk0tkD to see differences.

2. I removed a line that was left out in the wild and wouldnt let you start the app directly from the code as mentioned in discord

3. Changed all references of 'peek' to 'peak', grammatical error.

4. Y no manual refresh :(

Cool app ily

This adds an automated build of the compiled python code that can be downloaded and run, similar to a release zip. You can see an example of the build and download the artifact from: here

• checks out code
• installs dependencies (or downloads pip cache)
• installs cx_Freeze
• builds python executable
• zips compiled files b/c uploading files individually was slow
• uploads the zip as an artifact
• people can download the artifact from the Actions tab

Maybe it's not that useful b/c users can't customize anything but at least it shows the build process.

This results in a zipped zip file which requires two unzips. It is possible to upload all the 2000 files so that they are in one zipped artifact but it's painful to watch and takes about 4.5 minutes for that step to complete.

According to the announcement here, using rank yoinker might become bannable.

No personal profiles, scouting tools, guides based on individual players, or personalized data of any kind, UNLESS an individual player chooses to share their data. We want players to have ownership of their data, and we don't want to share it if that player doesn't want it shared. What this looks like can take multiple forms, but it will involve a Riot-owned authentication structure we can unlock for you if we believe your application design warrants it.

bcoz of riot tos we cant get ign of some players right, im suggesting, save data of last game to json maybe. we can save puuid right? and compare it to current game. and create new row lastgame. like this

Agent Rank LastGame Reyna. Plat. Chamber (blue box icon) Jett. Gold. None blue box means ally.

only a suggestion Thankss.

So i was testing this was working fine a few days back but more recently, past 2 days crashes my game saying a critical error has occurred and the process must be terminated after random intervals in game.

I have tried with both script and the application both cause the same problem. When im not running this im not facing any crashes.

v1.0.0

C:\Users\Glaived\AppData\Local\Programs\VALORANT rank yoinker>"VALORANT rank yoinker-Portable.exe"
Traceback (most recent call last):
  File "main.py", line 1, in <module>
  File "<frozen importlib._bootstrap>", line 1007, in _find_and_load
  File "<frozen importlib._bootstrap>", line 986, in _find_and_load_unlocked
  File "<frozen importlib._bootstrap>", line 680, in _load_unlocked
  File "PyInstaller\loader\pyimod03_importers.py", line 546, in exec_module
  File "requests\__init__.py", line 100, in <module>
  File "requests\__init__.py", line 85, in check_compatibility
Exception: You need either charset_normalizer or chardet installed
[636] Failed to execute script 'main' due to unhandled exception!

I've been using it for months but I think some random update on their end may have made it think the app is a trojan.

Says something about this line Gen:[email protected]

I'd like to be able to change the number of chat messages that are displayed at once by VRY, for me it's not super useful having only the last handful there. I'd rather customize it to fill the terminal with just enough space left over for the table.

The printed board if the console doesn't fit the columns amount is buggy, and it keeps being badly printed after resizing the window, unlike having the right size from the beginning (that requires the user to resize the console window asap after opening vry).

Maybe there's something that scales the board to the window size but it seems like it just breaks the board, even more after rescaling the window to a higher surface.

I could provide screenshots if it's not enough clear, but it can be easily reproduced, just enable all columns available (and even one more in immortal if the guy is on the leaderboard) without resizing the console after launch, and see the result on match 😅

The actual "already played with" caption needs some effort to find which one from the board is the one. Seeing people or agent name in a different color or with a specific thing on their line (a star or whatever) if I already played with them could maybe give that direct information 🤷‍♂️.

https://peps.python.org/pep-0008/

• [x] chatLogs.py
• [ ] colors.py
• [ ] config.py
• [ ] configurator.py
• [x] constants.py
• [ ] errors.py
• [ ] experimental.py
• [ ] Loadouts.py
• [x] logs.py
• [ ] names.py
• [ ] player_stats.py
• [ ] presences.py
• [ ] questions.py
• [ ] rank.py
• [ ] requestsV.py
• [ ] rpc.py
• [ ] server.py
• [ ] stats.py
• [ ] table.py
• [ ] websocket.py
• [ ] main.py
• [ ] setup.py
• [ ] CONTRIBUTING.md

Judging by our 3 different file naming conventions and countless more variable naming conventions, I think it's time to standardise.

After doing some research, I think we should go with pycodestyle; it uses the PEP 8 convention, which we started using with #115.