You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have a question about the projections. It may be a an error on my end, a bug, or need to alter the model.
I'm in a superflex (2qb) league. When entered the custom roster in and saved the settings, the resulting model placed QB1 Patrick Mahomes at rank 21. In every superflex ranking site I've seen (fantasypros, cbs, etc), Mahomes is ranked as #1 or #2 overall, with multiple other QB's going in the first round.
Is there something wrong I'm doing? Or is it something about the model I don't understand? I apologize if this method of communication was strictly for bugs, but I figured it's related to the model itself if it isn't a bug.
Thanks,
Chris
The text was updated successfully, but these errors were encountered:
Hi Chris, thanks for your message. As far as I can tell, this is not a bug--it's intended behavior based on the default value set for the QB "VOR Baseline" (see the "Draft Settings" section of the "Settings" page). You will want to increase the VOR Baseline for QBs. However, the bug we do have is that we the projection values don't seem to updating when modifying VOR Baselines, at the moment. We'll look into that. Thanks! @atungate@bison3
I have a question about the projections. It may be a an error on my end, a bug, or need to alter the model.
I'm in a superflex (2qb) league. When entered the custom roster in and saved the settings, the resulting model placed QB1 Patrick Mahomes at rank 21. In every superflex ranking site I've seen (fantasypros, cbs, etc), Mahomes is ranked as #1 or #2 overall, with multiple other QB's going in the first round.
Is there something wrong I'm doing? Or is it something about the model I don't understand? I apologize if this method of communication was strictly for bugs, but I figured it's related to the model itself if it isn't a bug.
Thanks,
Chris
The text was updated successfully, but these errors were encountered: