The NBA uses qualification thresholds for percentage stats. 300 field goals made for FG%. 82 threes for 3P%. 125 free throws for FT%. These numbers exist so a player who goes 2-for-2 from three does not lead the league at 100%.

Fair enough for a full season. 82 games. Months of data. The thresholds filter noise.

Shrink the window to January and those numbers collapse. Nobody hits 300 field goals in a month. The thresholds that protected signal become the thing that kills it. Every player fails qualification. The leaderboard empties.

What we changed

When a custom date range is active, qualification minimums are removed entirely. All players with games in the window are eligible. FG%, 3P%, FT% leaders reflect the actual sample. Small sample, yes. Misleading, possibly. But visible. The user chose the window. The data should respect it.

A quiet line appears below the stats table: Qualification minimums removed for custom date range. No modal. No tooltip. Just a fact.

Why it matters

Thresholds are not universal constants. They are calibrated to a specific scope. Change the scope, recalibrate the threshold. In our case, recalibrating to zero was the honest answer.