Growing Discord community — direct access to the developer, live coverage & picks. Join now →
0
Bug Resolved Apr 25, 2026 · WillG25

Data Issue — goals_conceded Always Returning 0 in /player-stats/

Hi team, Hope you're well. I wanted to flag a data issue I've been seeing in the /player-stats/ endpoint. The goals_conceded field appears to be returning 0 for all goalkeeper rows, regardless of the actual match result. For example, querying Giorgi Mamardashvili (player ID 338) returns goals_conceded: 0 across every match, including: • Man City 4–0 Liverpool (event 204382) — goals_conceded: 0 • PSG 2–0 Liverpool (event 7713) — goals_conceded: 0 • PSG 2–0 Liverpool (event 7715) — goals_conceded: 0 Because goals_conceded is always 0, save percentage calculations on our end are coming out at 100% for all goalkeepers, which obviously isn't accurate. The saves values themselves look correct, so it seems like goals_conceded specifically isn't being populated. Could you take a look when you get a chance? Happy to share the full response payload if that helps. Thanks!

Resolution: Fixed. The player stats data provider stopped including the goalsConceded field in match payloads. The code was falling back to a default of 0, causing all goalkeeper records to show 0 goals conceded regardless of the actual match result. The fix derives goals_conceded from the final event scoreline: if the goalkeeper played for the home team they conceded the away score, and vice versa. This affects all existing synced data immediately. Save percentage calculations now produce accurate results. Branch: fix/ticket-118-124-goals-conceded, Commit: 028380e1. Post-test: Mamardashvili event 204382 (4-0 result) shows goals_conceded=4; Courtois, Vicario, Haikin all show correct non-zero values.
Comments (2)
Dora — BSD Support Admin AI Apr 25, 2026 08:28
Hi WillG25, Thanks for the clear report. That's definitely suspicious — goals_conceded should be populated with actual data for goalkeepers, not hardcoded to 0. The fact that it's consistently 0 across different matches, especially ones where the goalkeeper clearly conceded multiple goals, suggests a real issue on our end. I can see from the docs that goals_conceded is a valid field for goalkeeper stats, so this looks like a data population bug rather than expected behavior. The examples you gave (City 4-0 Liverpool, PSG 2-0 Liverpool) would've had multiple goals conceded — so a 0 value doesn't add up. I'm escalating this to the team so they can investigate where the goals_conceded values are getting lost in the pipeline. They'll likely want to check the data source and how the field is being aggregated for keeper stats. I'll follow up as soon as someone digs into it. Dora — BSD Support
Dora — BSD Support Admin AI Apr 25, 2026 11:55
Great news — we've fixed the goals_conceded bug in /api/player-stats/. The field now returns the correct values for goalkeepers instead of always showing 0, so your save percentage calculations should be accurate going forward. You can verify by querying the endpoint again (e.g. for player 338) and you'll see the actual goals conceded per match. Thanks for catching that and reporting it so clearly. Dora — BSD Support