Bug Description
The attackdamageperlevel field for all champions in the Data Dragon JSON files is currently returning 0.
Problem Description
Following the release of patch 16.5.1, the champion data provided via the Data Dragon API contains incorrect scaling statistics. Specifically, the stats.attackdamageperlevel value is set to 0 for every champion, regardless of their actual in-game scaling. This breaks any calculation related to base AD at levels 2-18.
Expected Result
The attackdamageperlevel field should contain the correct numerical scaling value for each champion (e.g., 5 for Aatrox) to allow for accurate stat calculations at different levels.
Actual Result
The field is consistently returning 0 across all champion JSON files in version 16.5.1.
Example: Aatrox.json
Data snippet: "stats": { ... "attackdamage": 60, "attackdamageperlevel": 0 ... }
Developer Impact
Frequency: Every API call / All champions.
Severity: High. Any tool or site relying on Data Dragon for theorycrafting, damage calculation, or stat display is currently showing incorrect data.
Efficiency: Developers have to manually hardcode these values or revert to 16.4.1 data, which might be outdated for other balance changes.
Player Impact
Frequency: Constant.
Severity: Users of third-party scouting or theorycrafting sites see incorrect damage numbers, leading to confusion regarding champion power spikes and build efficiency.
Quantity: Potentially millions of players who use external companion apps or wikis.
Region: Global (all Data Dragon regions using 16.5.1).
Preconditions Requesting data from the 16.5.1 patch version of Data Dragon.
Repro Steps
- Access the Data Dragon endpoint for any champion in version 16.5.1: https://ddragon.leagueoflegends.com/cdn/16.5.1/data/en_US/champion/Aatrox.json
- Navigate to the data.Aatrox.stats object.
- Observe that "attackdamageperlevel": 0.
Issue Comments If you're also experiencing this issue, please confirm if other stats (like armorperlevel or mpperlevel) are also affected for you. This issue specifically impacts any project relying on accurate level-by-level stat scaling.
Bug Description
The attackdamageperlevel field for all champions in the Data Dragon JSON files is currently returning 0.
Problem Description
Following the release of patch 16.5.1, the champion data provided via the Data Dragon API contains incorrect scaling statistics. Specifically, the stats.attackdamageperlevel value is set to 0 for every champion, regardless of their actual in-game scaling. This breaks any calculation related to base AD at levels 2-18.
Expected Result
The attackdamageperlevel field should contain the correct numerical scaling value for each champion (e.g., 5 for Aatrox) to allow for accurate stat calculations at different levels.
Actual Result
The field is consistently returning 0 across all champion JSON files in version 16.5.1.
Example: Aatrox.json
Data snippet: "stats": { ... "attackdamage": 60, "attackdamageperlevel": 0 ... }
Developer Impact
Frequency: Every API call / All champions.
Severity: High. Any tool or site relying on Data Dragon for theorycrafting, damage calculation, or stat display is currently showing incorrect data.
Efficiency: Developers have to manually hardcode these values or revert to 16.4.1 data, which might be outdated for other balance changes.
Player Impact
Frequency: Constant.
Severity: Users of third-party scouting or theorycrafting sites see incorrect damage numbers, leading to confusion regarding champion power spikes and build efficiency.
Quantity: Potentially millions of players who use external companion apps or wikis.
Region: Global (all Data Dragon regions using 16.5.1).
Preconditions Requesting data from the 16.5.1 patch version of Data Dragon.
Repro Steps
Issue Comments If you're also experiencing this issue, please confirm if other stats (like armorperlevel or mpperlevel) are also affected for you. This issue specifically impacts any project relying on accurate level-by-level stat scaling.