Public leagues are open to all users and usually come from a template so everyone plays under the same structure. Private leagues are invitation‑only. They may be individual (one user tracked privately) or competitive (multiple invited users competing). Both types can be created from templates.
This rule sets how many plays a user may submit per day in this league. The limit resets daily. Once a user reaches the cap, no additional plays may be submitted in that league until the next day begins.
League behavior is defined by sport selection, default game counts, and how plays are constructed. These settings determine which games appear and how many must be included in each play.
A league may include one or more sports. Only games from the selected sports will appear in the available game list. Multi‑sport leagues combine all eligible games into a single pool.
This value sets how many games a user is expected to include in a play by default. It serves as the baseline unless overridden by a more specific rule such as flexPlay, allRequired, showAll, or random. Higher plans can raise the ceiling on this number - see the plans guide for the per-plan caps.
This sets the minimum number of games required in a play. Even if more games are available, a play cannot be submitted with fewer than this minimum.
Parlay leagues require multiple selections combined into one play. Parlays may use standard odds (spreads and totals), no‑odds scoring, or add‑unit adjustments (teaser‑style). Straight leagues use a single selection unless a rule requires multiple games.
All available games are shown, and the user may choose which to include. A minimum applies: at least two games for parlay leagues and at least two for straight leagues. This overrides the creator’s default number of games.
All available games are shown, and the user must include every one of them. If five games are available, all five must be selected. This applies to both parlay and straight structures.
The league's default number of games acts as a target size rather than a hard requirement. If there are enough games on the day's schedule, the play is built around that target number; if fewer games than the target are actually available, every available game is shown so nothing gets dropped. Unlike flexPlay, the user isn't choosing which games to include - the set is determined for them.
In random leagues, the system builds the user’s play automatically. Selection is random but guided. For example, a three‑leg random parlay using NFL and MLB games might include one MLB leg, one NFL leg, and one additional random leg. If the first two legs are both spreads, the final leg will be forced to be a total to ensure variety.
Start dates define when the league begins accepting plays. Options include: beginning of season (B.O.S.), today, beginning of week (B.O.W.), and beginning of year (B.O.Y.). These settings control the league’s initial active window.
End dates define when the league stops accepting plays. Options include: end of week (E.O.W.), end of month (E.O.M.), end of season (E.O.S.), and end of year (E.O.Y.). Season‑based leagues may include playoffs and can auto‑reset at season end while preserving the league and its membership.
A league can also be set up as an NFL Pick'em league instead of a daily-play league. Instead of a fresh play generated each day, members get the whole week's NFL schedule at once and fill it in at their own pace before each game locks at kickoff. See the Pick'em guide for how that works from the player's side.
Once a league exists, its owner can adjust a few additional settings that don't appear on the original creation form: the league's display timezone, whether same-day grading is allowed, and how close to kickoff a game remains eligible for picks (or whether live odds bypass that cutoff entirely). See Advanced League Settings for details.