8 facts that explain fantasy cricket form, injuries, lineup math, and scoring rules
Eight working facts a beginner can actually use. Each one shifts the credit math, the captain ladder, or the points engine. Skip the hype, build the lineup from the inputs you can verify.
A fantasy player walks into a contest 90 minutes before toss. The probable XI is out, the weather is logged at 32 degrees Celsius with 71% humidity, and the captain pick from the last match has a niggle. The player has 100 credits across 11 picks, two captain slots, and a five-minute reaction window between the toss and the first ball. Most of the contest is already decided by what they do next.
The micro-timeline for a typical contest runs in three beats. Beat one is the 24 hours before the match: squad lists, probable XIs, weather and pitch reads. Beat two is the five-minute toss window: the probable XI confirms or breaks, the captain pick has to lock, and a late scratch can rewrite the credit math. Beat three is the in-play window, where a quiet over can drop a lineup out of the money.
What follows are the eight durable facts that make that micro-timeline readable. None are time-sensitive. None depend on a current fixture. Each one is the kind of input a beginner can verify, attach to a name, and use the next time the contest window opens. The fantasy cricket working hub on Mycome Sports is the desk behind these facts.
What this explainer covers
- Fact 1: Where fantasy cricket news actually comes from
- Fact 2: Player form is three inputs that travel together
- Fact 3: Injury news lands late and most of it is noise
- Fact 4: The 100-credit salary cap is the real lineup rule
- Fact 5: Captain (2x) and vice-captain (1.5x) carry most of the ceiling
- Fact 6: Scoring rule changes live in the points engine, not the captain pick
- Fact 7: Lineup strategy is a reaction to the probable XI, not a prediction of it
- Fact 8: The credit math keeps winning over gut feel
Fact 1: Where fantasy cricket news actually comes from
Fantasy cricket news lives on a small ladder. The top rung is the official squad announcement, 24 to 48 hours before the match. The next rung is the probable XI from the desk or broadcast team, four to six hours before toss. The third rung is the weather and pitch read on match morning. The fourth rung is the late injury update from a beat reporter, the only rung that arrives inside the toss window.
The beginner trap is to treat all four rungs as the same input. They are not. A squad announcement is a closed list of available players. A probable XI is a desk's projection of which eleven names will take the field. A pitch read is a forecast. Read them in that order, with confidence decreasing as you go down.
Fact 2: Player form is three inputs that travel together
Form is not a single number. It is three inputs that have to move in the same direction before a captain pick is justified. The first is the last-five scores, weighted toward the most recent match. The second is the role in the current XI. The third is the venue and surface read. A 38-ball 70 on a flat track is not the same projection as a 38-ball 70 on a slow turner.
Beginners often anchor on the last-five number and ignore the other two. The reliable read is to require all three inputs to line up. Two positives and one neutral is a vice-captain candidate. One positive is a bench name. Three positives is a captain candidate. The test is the same across T20I, IPL and Hundred formats, which is why it travels without rewriting.
A single high score in the last-five can fool the credit math if the role in the XI has moved, or if the venue read has changed. The reliable captain read requires all three form inputs to line up on the same match.
Fact 3: Injury news lands late and most of it is noise
Injury news in fantasy cricket is dominated by two failure modes. The first is a soft rumour from a social account that names a player who is fit. The second is a hard rumour from a credible outlet that names a player who is rested for rotation rather than injured. Only the second is actionable, and only after the team confirms it inside the toss window.
Ignore social injury noise until the team confirms the change at the toss. A credible desk's probable XI already bakes in the soft rumours that have signal. If the probable XI still names the player, the soft-rumour weight is zero. The injury news that actually changes a lineup arrives in the toss window itself, and that kind is rare enough that waiting for it is a higher-EV move than chasing every pre-toss update.
Fact 4: The 100-credit salary cap is the real lineup rule
The 100-credit salary cap is the rule that decides almost every lineup choice before the captain pick is considered. Each player has a credit value set by the operator, and the eleven picks have to sum to 100 or less. Premium players cost 10 to 11 credits, mid-tier costs 8 to 9, and value picks cost 7 or below. Seven premiums will exceed 70 credits before any bowler is named.
The credit math is what turns a list of eleven good players into a single lineup. Two captains at 11, two premium all-rounders at 10, and three frontline bowlers at 9 already cost 92 credits, leaving 8 for the remaining four picks. The alternative starts with two premiums, two all-rounders and three mid-tier bowlers, freeing credits for a fourth batter or a second keeper. The captain pick is the call that comes after.
Credit math in one line: 2 captains at 11 + 2 all-rounders at 10 + 3 bowlers at 9 = 92 credits for 7 picks. The remaining 8 credits fund 4 value picks. Premium-heavy builds sacrifice the bench; balanced builds sacrifice the captain's upside.
Fact 5: Captain (2x) and vice-captain (1.5x) carry most of the ceiling
Captain and vice-captain are the only two multipliers in a standard fantasy cricket lineup. Captain scores count at 2x, vice-captain at 1.5x, and every other player counts at 1x. On a typical 300-point lineup, the captain contributes 60 to 80 of those points and the vice-captain contributes 30 to 50. Together they are roughly one-third of the total, which means the captain pick is the single largest variable in the contest.
Spend the most credit-analysis time on the captain pick, not on the value picks. A captain that hits 60 instead of 40 is worth more than three value picks that each hit 5 points above projection. The captain pick is the one decision that can lift a credit-balanced lineup into the top 10 percent of a contest, or sink it into the bottom half. The difference is often a single boundary or a single wicket.
Fact 6: Scoring rule changes live in the points engine, not the captain pick
Scoring rule changes are the inputs that quietly rewrite projections between formats. The points engine assigns points to runs, boundaries, wickets, catches, dot balls, strike-rate milestones and role-specific bonuses, and each operator updates the engine on its own schedule. A 4-point boundary bonus in one season may pay 5 in the next. A dot-ball bonus may be added. A strike-rate milestone at 170 may shift to 180.
Treat the points engine as the only source for scoring rules and never assume a bonus is unchanged across formats. A captain who clears the inner ring on a 4-point boundary bonus is worth less than the same captain on a 5-point bonus, and the difference compounds across an innings. Re-reading the engine at the start of the season and again on every mid-season edit is the habit that keeps the credit math honest.
Boundary bonuses and dot-ball bonuses are the scoring rules that move a captain's projection the most. Mid-season edits are the moments to re-read the engine rather than assume last season's math still applies.
Fact 7: Lineup strategy is a reaction to the probable XI, not a prediction of it
Most lineup mistakes come from trying to predict the XI instead of reacting to it. The probable XI is published hours before the match. The confirmed XI arrives at the toss. The fantasy lineup locks a few minutes after, and the lock window is roughly five minutes. Trying to out-predict the probable XI inside that window is the move that costs the most credit math, because the fantasy player over-corrects on the captain pick.
Build a default lineup from the probable XI and use the five-minute lock window for a single targeted edit. If the confirmed XI matches, no edit is needed. If a single player is dropped, the edit is one swap. If the captain pick himself is dropped, the edit is two swaps and the new captain is the next-highest probable XI name. The default-then-react flow keeps the credit math stable.
Default-then-react workflow: build from the published XI · wait for the confirmed XI at toss → swap one player for a scratch, or swap the captain if the captain is scratched → lock. Do not rebuild inside the lock window.
Fact 8: The credit math keeps winning over gut feel
The final fact ties the other seven together. Across long fantasy cycles, the credit math wins out over gut feel more often than not. A lineup built on the published probable XI, the three-input form test, the confirmed injury read, the 100-credit cap, the captain multiplier, the points engine read, and the default-then-react flow will, over a season, return a higher hit rate than a lineup built on a single gut-feel captain pick. Durable wins.
The reason the credit math wins is that every input it leans on is verifiable. A credit value is published. A captain multiplier is fixed by the rules. A points engine entry is published. A probable XI is published with a desk attached. Gut feel is the only input without a source, and inputs without a source produce picks with no error bar. The credit math puts an error bar on every pick. That is the edge.
The credit math also produces a clear next step. The most reliable improvement a beginner can make between two contests is to read the points engine once, count the captain and vice-captain multipliers in their last lineup, and add up the credit cost of the premium picks. Apply that diagnosis to the next contest window.