Frequently Asked Questions

1. Create a free account and confirm your email address.
2. Open the NFL Builder, choose Classic or Captain Mode, and click the slate you are entering.
3. Edit FPPG for the players you have a read on, trash players you do not want, and set exposure in the player table.
4. Choose how many lineups to build and click SUBMIT.
5. Review the build, prune or edit it, and download the CSV to upload to DraftKings.

The How It Works page walks through each step with every control explained.

Not to try it. The demo builds up to 3 lineups on the current main slate with no account. A free account unlocks every slate and up to 20 lineups per build; you confirm your email address before the first login.

The account also holds your Builder Defaults: the defaults every new build starts from: lineup count, minimum salary, auto-trash rules and, with the Season Pass, every builder setting (stacks, bring-back, volatility and lineup rules) plus per-position max exposure.

RotoCore currently supports DraftKings NFL contests:

• Classic: nine-slot lineups (QB, RB, RB, WR, WR, WR, TE, FLEX, DST) on any classic slate, from the full main slate to two-game primetime slates.
• Captain Mode: single-game Showdown slates with one Captain (1.5x points, 1.5x salary) and five FLEX slots from either team.

Slates, salaries, positions, player IDs, and FPPG come from DraftKings. Game spreads and totals come from the betting market, and the implied team totals (ITT) in the player table are derived from them. Injury designations come from the official NFL injury report, cross-checked against a second source. They are refreshed between full syncs, but they are not game-time updates — always verify player status before you enter.

A full sync runs several times a day, with separate injury and odds refreshes in between. If a slate's data is older than it should be, a notice appears at the top of the builder so you know before you build.

No. DFS involves risk, and no lineup builder or projection can guarantee a profit.

RotoCore builds the best lineups it can from the numbers and rules you give it. The quality of the lineups depends on the quality of those inputs. Please play responsibly.

No. FPPG is each player's DraftKings average of actual fantasy points per game this season, exactly as DraftKings shows it. RotoCore does not produce projections of its own and does not pull them from anywhere.

The column is editable so you can replace the average with your own number: type a value or move it 5% at a time, and the build uses what you entered. With the Season Pass you can also upload a CSV of your own projections.

Yes, with the Season Pass. Open a slate, click PROJECTIONS above the player table and choose a CSV with a player column (names, or DraftKings ids) and a projection column; a team column helps with lookalike names. Or download the template for the slate from the same menu: it lists every player with the DraftKings average filled in, so you only change the numbers you have a view on.

You see a preview first: which players would change and by how much, and which rows did not apply and why; you can point an unmatched row at the right player, and that spelling is remembered in your browser. Nothing changes until you click Apply. Matched players then take your number as their FPPG baseline for that slate and everyone else keeps the DraftKings average. In Showdown the CPT row shows 1.5x your number. Clear projections puts the averages back.

The file is read once and the values stay in your browser for about a week, never on our servers. The no-account demo does not have it.

In every lineup: set the player's Min Exp to 100. He will be in every lineup the build produces.

Out of the pool: click the X on his row to trash him. The TRASH button shows how many players are out and opens a list where you can restore anyone.

Out in bulk: the Auto Trash menu removes everyone under a salary or FPPG threshold, or everyone carrying a chosen injury status, in one click. Your Builder Defaults page can apply the same rules automatically whenever a slate loads.

Min Exp and Max Exp on each row are the share of your lineups a player must and may appear in.

• Min 50, Max 70: a core play, in half to two thirds of the build
• Min 0, Max 30: a pivot, in no more than 30% of lineups
• Min 100: in every lineup

Caps are paced across the build rather than front-loaded, so a 50% player alternates through the lineups instead of filling the first half and vanishing from the second.

Two related settings: the Season Pass adds per-position max exposure defaults on the Builder Defaults page, which seed the Max Exp column when a slate loads, and a Team exposure rule that caps how many lineups any one team may appear in.

Stacking means rostering players whose scoring is correlated, usually a quarterback with his own pass catchers: when he throws a touchdown, both score. It raises a lineup's ceiling, which is what tournaments reward.

The Stacks tab (Season Pass) offers SINGLE, DOUBLE, TRIPLE, and QUAD (a QB with one to four pass catchers) and RB & DST (a running back with his own defense). Enable one or more shapes and every lineup carries one of them around its QB. The percentage on each shape caps how often any one team's stack of that shape may appear across the build. A checkbox lets running backs count as stack partners.

Stacks apply to Classic slates. Showdown lineups already draw from both teams. See the Strategy Guide for how to use each shape.

Volatility (Season Pass) nudges every player's FPPG up or down by up to the chosen percentage, freshly for each lineup, so the solver does not keep landing on the same handful of players. The slider runs from 0% to 30% with three presets:

• Cash (0%): every lineup is built straight off your FPPG numbers
• Balanced (10%): the default, a modest spread
• GPP (20%): a wide spread for tournament builds

Free accounts build at the 10% default.

Cash games: 1 to 3. You only need one good lineup, so build a few and pick.

Small tournaments: 20 to 50, enough to spread across a few stacks and pivots.

Large tournaments: up to the contest's entry limit, commonly 150 for the biggest DraftKings GPPs.

Free accounts build up to 20 lineups per run; the Season Pass raises that to 150. Every lineup in a build is unique: no two share more than the number of players your Unique players rule allows.

Yes. View Lineups opens the build in the Lineup Editor, one row per lineup. You can name the build, remove or duplicate selected lineups, and save. Build Results shows player usage and statistics for whatever the build currently contains.

Compare puts two builds from the same slate side by side and lets you copy lineups from one into the other, so you can assemble a final set from several builds with different settings.

Pruning trims a build to a target count without rebuilding. In the Lineup Editor, enter how many lineups to keep, choose a strategy, and click Preview to see how many would go before you apply it.

• Top FPPG: keeps the highest-FPPG lineups
• Most Different: keeps the lineups that share the fewest players, leaning toward FPPG
• Spread Exposure: cuts the weakest lineups of the most-used players until no one dominates
• Stack Variety: keeps the best lineups from every QB stack, or every captain in Showdown

Typical use: build 150, prune to the contest's entry limit. The Strategy Guide has workflows for cash and tournaments.

With the Season Pass, click CSV in the Lineup Editor, the build history panel, or the comparison view. The file is in DraftKings' bulk-upload format with the correct player IDs. Then:

1. Log in to DraftKings and open the contest.
2. Choose the bulk upload option (labeled "Upload lineups" or similar depending on the page).
3. Select the file. DraftKings creates one entry per row, up to the contest's entry limit.
4. Review the entries and confirm.

Free accounts can build and review lineups but not download the CSV.

No. The Season Pass is a one-time payment. There is no subscription and nothing to cancel.

Access runs through the end of the NFL season shown on the pricing page. When the next season comes around you can choose to buy a new pass.

Payments go through Stripe Checkout, which accepts all major credit and debit cards.

Card details are entered on Stripe's page and never touch our servers. Receipts and purchase history are available from your profile.

Yes, within 7 days of purchase, no questions asked. Email us from the address on your account and we refund the full price to the original payment method.

After 7 days the pass is non-refundable except where the law requires otherwise. Full details are in the Refund Policy.

The rules you set left too few valid rosters. Common causes:

• A stack shape larger than your Players per team cap (a QUAD needs 5 from one team)
• Unique players set high on a small slate, so the pool runs out of different lineups
• Tight Max Exp values on many players at once, or a low Team exposure on a two-game slate
• Too many players trashed, especially at a thin position like TE or DST
• A minimum salary so high that few rosters can reach it

Contradictory settings are caught before the build starts with a message saying what to change. If the build could only produce some of the lineups, you get those, flagged as partial, and can loosen a rule and run again.

Saved to your account: the defaults on your Builder Defaults page: lineup count, minimum salary, unique players, auto-trash thresholds and injury statuses, and (Season Pass) the full builder panel of stacks, bring-back, volatility and lineup rules, plus per-position max exposure. They apply every time you open a slate and can be changed per build.

Saved in your browser: build history. The 20 most recent builds are kept, plus up to 5 you protect with the lock button, for a week. Older unsaved builds drop off as new ones arrive, and the history does not follow you to another device or browser.

Per session: FPPG edits, exposure values, and the trash list for the slate you have open. They reset when you reload or click RESET, so export a build you want to keep.

The site works in a phone or tablet browser and the tables scroll sideways.

The player table has a lot of columns and the lineup editor shows nine slots per row, so a desktop or a tablet in landscape is the better experience for editing a big build.

1. Read the message. Most errors name the setting to change.
2. If you see "too many requests", wait a few minutes. Builds are rate-limited per account to keep the site responsive for everyone.
3. Refresh the page and try again. Your build history is still there.
4. Make sure your browser is current. Chrome, Firefox, Safari, and Edge are supported.
5. Still stuck? Send the details through the Contact page: the slate, what you clicked, and the message you saw.

• We never ask for your DraftKings login. The builder reads DraftKings' public contest data and gives you a file to upload yourself.
• All traffic is encrypted over HTTPS.
• Passwords are hashed and never stored in plain text.
• Payments are handled by Stripe. Card numbers never reach our servers.
• Your settings are private to your account.

See the Privacy Policy for details.