I’m primarily a small-field tournament player and will use this space to discuss specific players and roster constructions that I’m targeting on the FanDuel main slate in Week 10.
This week’s article will have a different format than we’ve been using. Below I will walk through an example of how I use the RotoViz DFS Lineup Optimizer. It is important to remember that no optimizer gives you answers to the test, but is a tool that you must use properly.
Step 1: Exclude Bad Plays
The RotoViz Lineup Optimizer is powered by GLSP projections. You can understand how GLSP projections are created here, but one pitfall to using entirely automated projections is they can miss on players with changing circumstances. The first thing I do when I open the DFS Lineup Optimizer is exclude injured players.
On this first run of excluding players, I don’t try to cut down my player pool too much. I really just want to limit this first cutdown to the players I obviously want 0% exposure to. I will do this for each position.
Step 2: Customize Settings
Next I set my global rules. The rules I use will vary by slate context and contest size. Here is an example of how I use customize settings for small field tournaments in the FanDuel Week 10 main slate.
- Max exposure 80%. Remember that this is a global setting – you can fine tune any individual player to have less than this max.
- Maximum 6 repeating players. at least 3 of the 9 roster slots have to be different between any two teams generated.
- Leave no more than $400 on the table.
- Always want to stack a QB with a WR. On some slates you may not want to check this if you think a QB can be stacked with just a RB or TE. However, I will almost always want to include a WR in a stack.
- RB only in Flex. In small field tournaments on FanDuel I always default to RB in the Flex. That is certainly slate and contest specific though.
- 10% Randomness is my standard.
- I tend to avoid opposing defenses with my skill position players. But this is a setting that my adjust depending on the slate.
- I’ll elect to not force a QB with an opposing WR. Instead, I will build my bring backs through the Groups function.
