[BUG] `match-v5` fields `playerAugment5` & `playerAugment6` are always 0

[1337MARCEL]

Bug & Problem Description
It seems that when introducing more than 4 augments in the Arena & Swarm game mode, the playerAugment5 & playerAugment6 field is not working as expected and returns 0 even though a player has selected a 5th/6th augment.

For example, in match NA1_5246867453, the player playing Ziggs had 5 augments at the end of the game, but the API returns 0 for playerAugment5.

Developer Impact

• Frequency: Could not find any games in our database where playerAugment5 or playerAugment6 is anything other than 0.

[Juskocode]

Issue: Inconsistent Null Values in playerAugmentX Field in matchv5 API Responses

Description
When querying the Riot Games API (matchv5 endpoints), the playerAugmentX field consistently returns null across tested matches. Initial testing suggests that this behavior persists in most cases, requiring a large-scale extraction of matches to identify instances where the field is populated. This inconsistency may indicate either undocumented conditions for data availability or a potential API issue.

Steps to Reproduce

1. Request match data via the matchv5 API (e.g., GET /lol/match/v5/matches/{matchId}).
2. Inspect the playerAugmentX field in participant data.

Expected Behavior
The playerAugmentX field should contain relevant data (e.g., player-specific arguments or metadata) when applicable to the match or game mode.

Actual Behavior
The playerAugmentX field is consistently null, even in matches where its usage might be expected (e.g., special game modes or events).

Additional Context

• Observed across multiple regions and match types.
• No clear documentation on conditions under which playerAugmentX is populated.
• Large-scale data extraction might be required to identify edge cases, suggesting either rare usage or a systemic issue.

Request for Clarification

1. Is the playerAugmentX field intentionally deprecated or unused?
2. Are there specific game modes, regions, or match conditions where this field is populated?
3. If this is a bug, can the Riot API team investigate the root cause?

Example Response Snippet

{
  "participants": [
    {
      "playerAugmentX": null, // Always null in tested cases
      // ... other fields
    }
  ]
}

Proposed Follow-Up

If this is unintended, I recommend:

• Investigating API logging or backend checks for missing data.
• Updating documentation to clarify the field's purpose and expected values.
• Possibly extract large data and check if this errors persists.

[MGSimard]

++ For a billion dollar company, I'd expect more importance placed in having correct endpoint documentation. The endpoint docs are littered with incorrectly filled types, lack of possible nullish instances or straight up missing fields. Consistent issue with Riot devrel for years.

PS: Here's an example from a while ago; Ctrl+F "Missing from docs", both playerAugment 5 & 6 were problematic a while ago already.

https://github.com/MGSimard/leaguemh-next/blob/main/src/lib/typesMatchV5.ts

[Juskocode]

So let's develop a good API together 😍