[FEATURE REQUEST] return TFT b-patches as part of tft_match info response body

[orlandosh]

Problem Description
When I request a match by its ID, game_version returns "Version 13.18.530.4653 (Sep 07 2023/19:32:41) [PUBLIC]". However, the current tft version is not from Sep 07, it's from Sep 15th.

Expected Result
I was expecting the version to correctly indicate the date, Sep 15th, so my app can detect it's a new b-patch.

Actual Result
Version 13.18.530.4653 (Sep 07 2023/19:32:41) [PUBLIC]

Developer Impact
Describe how this affects you as a developer. Please include the frequency and severity of the issue.

• Frequency: Every API call.
• Severity: When it happens, my program does not know how to handle pre or post b-patch updates, leading to inconsistent data.
• Cost: Requires me to manually find another way of defining when a b patch starts. That could be checking tft staff twitter for mentions of a b patch, or maybe checking riot's patch notes and seeing if the html file changed. note: I haven't done any of that, as I don't know if it's allowed or not. I would only do it with permission from riot games beforehand.
• Efficiency: Requires me to either use twitter's api or make http get requests to riot games patch notes every hour (I don't know if that's allowed, so I haven't done any of that)
• User emails: app currently in development.
• Etc

Player Impact
Describe how this affects League of Legends players. Please include the frequency and severity of the issue.

• Frequency: This leads to users seeing incorrect information about their current match patches as well as data regarding comp clustering & stats.
• Severity: When this bug happens, my website might become less trustworthy as it doesn't display the correct patch.
• Quantity: it's still in development as a pet project
• Region: This affects players worldwide
• Etc

Preconditions
What conditions must be met in order for this bug to occur?

• query riot api tft_match endpoint after a b patch is live

Repro Steps
Step by step, what do you need to do to cause the bug? Note that GitHub will automagically number each step if you prefix the line with "1. "

1. query riot tft_match after a b patch is live

Issue Comments
This is an unexpected issue. I actually created a system to detect when a b-patch is live through the api response but I say that the responses haven't changed, so the game version field ends up not being useful for b-patches. I will probably have to contact riot api support to find a compliant way to detect b patches automatically, as doing it manually is not viable either. I haven't explored the in-game API as an standalone app is still not part of my roadmap.

[bangingheads]

This is the correct game client version as noted in the documentation of the field.

This would be more of a feature request to include this data than a bug.

[orlandosh]

This is the correct game client version as noted in the documentation of the field.

This would be more of a feature request to include this data than a bug.

Thanks for pointing it out, updated accordingly.