Fantasy cricket, treated like a craft.
A complete reading order: rules, salary cap math, captaincy logic, contest formats, and a daily shortlist, written for the way Indian readers actually play.
A reading order for fantasy cricket, treated like a craft.
Read top to bottom for the full chapter, or jump in at the section that matches the question you have right now. Every subtopic opens on its own page; nothing here is a stub.
The rules, in one read
How fantasy cricket works on every Indian platform: salary cap, captain multiplier, role limits, and the bits the small print hides.
02Captain and vice-captain math
Why 2x and 1.5x are not equal, and how to find captaincy value without copying the crowd.
03The points system reference
Every number a platform scores, in one table. We update it whenever a platform changes a number.
04Contest formats
Head-to-head, mega, practice, winner-takes-all, season-long, and stock-style. The honest trade-offs of each.
05Toss and pitch reading
How to read a pitch report in three minutes, and what to change in your team if the toss goes against you.
06The withdrawal walkthrough
KYC, PAN, UPI, and the rare cases where a payout stalls. A clean checklist for first-time withdrawals.
The full chapter, in one read
Fantasy cricket looks like a slot machine from the outside: pick eleven names, watch a match, hope the points line up. Read the rules carefully and the format reveals itself. The platform takes a real fixture, scores every action on a published matrix, and lets you assemble a virtual XI inside a salary cap. The cap forces trade-offs. The trade-offs force opinions. The opinions, over a season, are what decide who wins.
The reading order below is the one we use internally when a new editor joins the desk. It is not a sales funnel and not a glossary. It is the path that, in our experience, gives a new player enough framework to read the rest of the desk without misreading the predictions or the points table.
What you should do next
The fastest way to use this chapter is to read the first subtopic, then jump to whichever subtopic matches the question on your mind. If you are new, the captain and vice-captain subtopic is the one that pays for itself the soonest. If you are returning, the salary cap math subtopic is usually where the season-end edge sits.
We update this chapter weekly. The date below the headline is the last refresh; the changelog at the bottom of the guide records every substantive change.
The reading order, in detail
The reading order starts with the rules, because the rules are the only part of the format that is fixed across every Indian platform. The rules are simple: pick eleven players inside a 100-credit salary cap, with role limits, and a captain and vice-captain who earn 2x and 1.5x. The rules take ten minutes to read and ten minutes to internalise. Once you have the rules, the rest of the format is a series of choices.
The captaincy math is the second part. The 2x and 1.5x multipliers are not equal, and the difference is where the season-end edge sits. The right captain pick is not the most popular pick; the right captain pick is the player with the strongest case for the next match, with the case built from the data on the desk. The captaincy call is the single most important decision in a fantasy contest, and the desk logs every call.
The points system is the third part. The points matrix is published by every platform, and the differences between platforms are small but real. The T20 column is the one that matters for the IPL; the ODI and Test columns are useful for the international fixtures. The desk publishes the full reference on the fantasy tips page.
The contest formats are the fourth part. Head-to-head, mega, practice, winner-takes-all, season-long, and stock-style. Each format rewards a different kind of team. The desk publishes a per-format recommendation on the fantasy tips page, with the reasoning and the trade-offs.
The toss and pitch reading is the fifth part. The toss call, the dew read, and the pitch map are the inputs that change the captaincy call after the team is built. The desk publishes a per-venue pitch map on the fantasy tips page, with the data from the last 14 completed T20s at the venue.
The withdrawal walkthrough is the sixth part. The KYC, the PAN, the UPI handle, and the rare cases where a payout stalls. The desk publishes the full walkthrough on the withdrawal page, with the contact list and the support hours.
More from the desk.
Questions readers ask before they read the chapter.
-
How long will it take to read this chapter? Plan on 18 to 25 minutes for the full chapter, including the subtopic pages. The summary at the top is two minutes if you only need the headlines. -
Is this chapter written for beginners or returning players? Both. The first subtopic is the beginner path. The salary cap and contest format subtopics are written for players who already play and want to sharpen. -
Do you take affiliate revenue from the platforms you cover? Yes, and we disclose every commercial relationship on the responsible play page. Editorial coverage is independent of commercial relationships; the desk does not promote a platform it would not play on itself.
The five-question framework, in detail
The five-question framework is the method the desk uses for the daily shortlist. The first question is about the death-overs bowler: who bowls at the death for the chasing side? The second question is about the venue: is the venue a batting paradise or a spin trap? The third question is about the head-to-head: what is the captain’s record in this exact matchup? The fourth question is about the squad: are any frontline allrounders rested? The fifth question is about the format: is the contest rewarding ceiling or floor? The five questions are answered in order, and the answer to the fifth question is the captaincy call.
The points matrix, in detail
The points matrix is published by every platform. The differences between platforms are small but real. The T20 column is the one that matters for the IPL; the ODI and Test columns are useful for the international fixtures. The desk publishes the full reference on the fantasy tips page, with the differences between platforms highlighted. The matrix is updated within an hour of any platform change.
The contest format comparison, in detail
The contest formats are head-to-head, mega, practice, winner-takes-all, season-long, and stock-style. Each format rewards a different kind of team. The head-to-head rewards floor; the mega rewards ceiling; the practice rewards learning; the winner-takes-all rewards variance; the season-long rewards consistency; the stock-style rewards active trading. The desk publishes a per-format recommendation on the format explainer, with the reasoning and the trade-offs.
The reading order for the month, in detail
For a typical IPL month, the reading order is: Monday, the squad announcements; Tuesday, the daily shortlist and the fantasy value lists; Wednesday, the long-form piece on the desk; Thursday, the captaincy call for the next match; Friday, the weekend reading; Saturday, the live tracking; Sunday, the review. The reading order helps balance the time commitment with the editorial coverage. The order is not a rule; the order is a starting point.
How the editorial desk keeps this guide accurate
The editorial desk re-verifies the content on this guide every week. The re-verification covers the source data, the platform’s published T&C, and the support team’s published workflow. If any of the three changes, the page is updated within an hour. The date at the bottom of the guide is the last refresh; the changelog at the bottom of the guide records every substantive change. The desk does not publish a page that fails the re-verification; the guide is taken down or rewritten until it passes.
The editorial desk uses a four-step re-verification process. Step one: the source data is checked against the public database. Step two: the platform’s T&C is checked against the platform’s own published version. Step three: the support team’s published workflow is checked against the support team’s most recent email or chat response. Step four: the editorial content is checked against the three sources. The four steps are the minimum; the desk does not skip a step.
What to do if you spot an error
If you spot an error on this guide, send a one-line email to [email protected] with the subject line “Fact correction”. The desk will verify the error against the source data and will publish a correction within 24 hours. The correction is logged in the changelog at the bottom of the guide, and is communicated through the in-app notification and the support email. The desk takes fact corrections seriously; the corrections are the most important kind of contact the desk receives.
If the error is a typo, the desk will fix the typo within 24 hours. If the error is a mislabelled venue, a mislabelled captain, a mislabelled date, or a mislabelled team, the desk will fix the mislabelling within 24 hours. If the error is a structural issue with the editorial content, the desk will rewrite the relevant section within 48 hours. The desk does not publish a correction that introduces a new error; the correction is verified against the source data before it is published.
How the desk handles commercial relationships
LeagueX carries affiliate links to the platform’s own app. The affiliate links are clearly labelled, and the editorial coverage is independent of the affiliate revenue. The desk does not run sponsored content, does not run a paid-placement programme, and does not accept payment for editorial coverage. The full disclosure is on the responsible play page. The desk’s commercial relationships are limited to the affiliate programme; the desk does not have any other commercial relationships with the platform or with any other party.
The desk’s editorial standards are independent of the affiliate programme. The standards are: the sources are cited, the reasoning is shown, the misses are logged, the commercial relationships are disclosed, and the corrections are published. The five standards are the basis of the editorial coverage; the desk does not publish a piece that fails any of the five standards. The standards are the same across every chapter and every article on the site.
The five editorial standards, in detail
Standard one: the sources are cited. Every fact, every figure, every number on the desk is traced to a public source. The source is cited in the text, in the changelog, and in the verification log. The desk does not publish a fact that cannot be traced to a public source. Standard two: the reasoning is shown. Every prediction, every shortlist, every captaincy call is published with the reasoning that produced it. The reasoning is shown in full, not summarised. Standard three: the misses are logged. Every prediction, every shortlist, every captaincy call is logged, and the misses are published at the end of the season. The misses are the most important data point on the desk.
Standard four: the commercial relationships are disclosed. The desk discloses every commercial relationship that affects the editorial coverage. The disclosure is on the responsible play page and on the about page. The disclosure is updated within an hour of any change in the commercial relationships. Standard five: the corrections are published. Every fact correction is published within 24 hours, and is logged in the changelog at the bottom of the relevant page. The corrections are the most important contact the desk receives; the desk treats the corrections as a quality check on the editorial coverage.
What to read next
If you want to keep reading, the fantasy cricket reading order is the most useful starting point. The reading order covers the rules, the captaincy math, the points system, the contest formats, the toss and pitch reading, and the withdrawal walkthrough. The reading order is designed for new and returning players, and is updated weekly. If you want to play, the download path is the fastest one. The free practice contests are open all year and do not require a deposit. The editorial calendar is on the same URL every week.
If you have a specific question, the contact page goes to a real person on the desk. The desk answers within two working days. The contact list for the platform’s support team is on the customer care page. The desk does not have access to the platform’s support channels; the desk and the support team are independent. The editorial coverage is independent of the platform; the desk does not promote a platform it would not play on itself.