[Bug]: n_times_thru_order Column

[kfran19]

The ntimes_thru_order column isn't 1,2,3,4 its,1,2,3,4, 21,22,23,24.....32,33,34,35 etc. how can this be corrected

[saiemgilani]

Duplicate of #413 / #408, fixed today by #412 (merged to master). Root cause: Baseball Savant inserted a new miss_distance column mid-frame (between swing_length and estimated_slg_using_speedangle), which shifted the positional column rename by one for every column after it — n_thruorder_pitcher sits right after age_bat, so it was receiving batter ages (the 21–35 values you saw). Verified live on current master (2026-07-21 slate, 3,870 pitches): n_thruorder_pitcher returns 1–3 and miss_distance comes through under its own name. The fix is not in a CRAN release yet — install the dev version: pak::pak("BillPetti/baseballr") (or devtools::install_github("BillPetti/baseballr")). Reopen if you still see it after updating.

[kfran19]

Duplicate of #413 / #408, fixed today by #412 (merged to master). Root cause: Baseball Savant inserted a new miss_distance column mid-frame (between swing_length and estimated_slg_using_speedangle), which shifted the positional column rename by one for every column after it — n_thruorder_pitcher sits right after age_bat, so it was receiving batter ages (the 21–35 values you saw). Verified live on current master (2026-07-21 slate, 3,870 pitches): n_thruorder_pitcher returns 1–3 and miss_distance comes through under its own name. The fix is not in a CRAN release yet — install the dev version: pak::pak("BillPetti/baseballr") (or devtools::install_github("BillPetti/baseballr")). Reopen if you still see it after updating.

I have used
pak::pak("BillPetti/baseballr")(ordevtools::install_github("BillPetti/baseballr")
restarted session and then ran data refresh from beginning of season and all this numbers show up again