The Int16 Skin ID API Failure
Why Paladins skin IDs above 32,767 break the Hi-Rez match API, with a database-sourced list of known affected skins.
Published: July 2026 | Topic: Data integrity · Game analytics · Hidden bugs
The Problem
Some Paladins skin_id values now exceed the signed 16-bit integer maximum of 32,767, but part of the Hi-Rez match-data path still attempts to deserialize the field as an Int16. The value cannot fit, so the API emits an explicit error message instead of returning the affected player row:
Value was either too large or too small for an Int16. Failing Field = skin_id
What happens above the boundary?
The failure is not silent. When a positive skin ID exceeds the Int16 limit of 32,767, the Hi-Rez API returns an Int16 error and drops the match data.
Known Broken Skins
The list below was fetched from existing PaladinsCat database records. It contains observed skin IDs above the signed Int16 boundary.
Database snapshot: 31 known broken skins across 20 champions (July 2026).
Affected Skins
31 confirmed broken skins across 20 champions:
Near-Miss Skins
Five skins were flagged as false positives by other groups but confirmed safe — their IDs remain below 32,767:
Boundary Summary
Int16 max (signed): 32,767
Current highest ID: 33,769
Continue reading
Beyond the Int16 Overflow: Recovering the Match Hi-Rez Drops → follows the failure into the raw Hi-Rez payload and shows how PaladinsCat reconstructs the players that disappear after the Int16 sentinel.
The listed skin IDs and champion names were fetched from existing PaladinsCat database records and reflect data available in July 2026.