Mike Filicicchia

That needs no updates. Fumbles lost are already in there. They just aren't showing up in the df output of ff_scoringhistory(). That's what I meant when I said there was...

I’m still confused because the mapping here includes all 3 types of fumbles lost for MFL.

Here's what I'm getting: ``` names(ffscrapr::ff_scoringhistory(mfl_connect(season = 2021, league_id = 22686, rate_limit_number = 3, rate_limit_seconds = 6), season = 2019:2021)) [1] "season" "week" [3] "gsis_id" "sportradar_id" [5] "mfl_id" "player_name" [7]...

OH WAIT! Is ff_scoringhistory() written so that it only includes variables that are used in your particular league's scoring system? That explains to me what's going on here. What do...

> Better would be adding an optional argument that would provide an ff_scoring dataframe to use instead of the original. Busy, but can stick onto the backlog Ooo yeah, good...

Would that argument affect the points variable and how it’s calculated, the variables passed to the output df, or both? And if it’s left blank, what happens? I guess I’m...

I'm seeing that now, yes. Ok, I think this is different than before, but yes it looks constrained by what I choose to have displayed. Is there a way for...

``` ── System Info ──────────────────────────────────────────────────────────────── • R version 4.4.1 (2024-06-14 ucrt) • Running under: Windows 11 x64 (build 22631) ── Package Status ───────────────────────────────────────────────────────────── package installed cran dev behind 1 ffscrapr...

``` str(ff_standings(mfl_connect(season = 2022, league_id = 22686, rate_limit_number = 3, rate_limit_seconds = 6))) tibble [32 × 13] (S3: tbl_df/tbl/data.frame) $ franchise_id : chr [1:32] "0005" "0019" "0027" "0028" ... $...

Oh wow, this is dumb. It was because I wasn't capitalizing the F in "fire". Didn't realize this was case-specific. Thanks.