Cricket laws every fan should know, and why they exist

Somebody in the room always says it. The ball thudded into the pad in front of middle stump, the bowler is on his knees, three replays agree that it was heading into the top of leg, and the umpire does nothing at all. The reason, when it arrives on screen, is that the ball pitched about two centimetres outside the line of leg stump. It looks like a technicality wearing the costume of a law.

It is not a technicality. It is an answer to a specific unfairness, written down by people who had watched somebody exploit it. That is the pattern behind almost all of the cricket laws every fan should know: each one closes a gap that a bowler, a batter or a captain had already walked through, and the gap is usually easier to remember than the wording.

Learn the reasons and the laws stop being a list. They become a set of decisions about what counts as a fair contest between one player trying to hit three sticks and another trying to stop them with a piece of willow.

The cricket laws every fan should know are answers, not instructions

The code is maintained by the Marylebone Cricket Club, which has been its custodian since the eighteenth century and remains the only body permitted to change it. There are forty-two laws. They are written in continuous prose rather than numbered bullet points, they define their own vocabulary as they go, and they can be read end to end by anybody who wants to, free, in an afternoon.

That drafting style is doing something. A football rule tells a referee what to punish. A cricket law tends to tell an umpire what the game is trying to protect, then works outward to the cases. This is why the code survives contact with situations nobody anticipated: an umpire who understands the purpose of a clause can apply it to a circumstance the drafters never imagined.

Three quick illustrations of the pattern, all of which get their own treatment below.

A batter may not be given out leg before if the ball pitched outside leg stump, because from that angle the batter's legs are between the ball and the stumps whether they like it or not.

A delivery the batter cannot reach is called a wide, because without that rule the safest ball to bowl at a set batter would be five yards down the leg side, every over, forever.

An incoming batter must be ready to face within a fixed time, because cricket has no clock, and a game with no clock and no arrival deadline can be stalled indefinitely by whichever side finds delay convenient.

None of those three is arbitrary. Each is a fix, and the fix is the memorable part.

• 42Laws in the current code
• 10Methods of dismissal
• 5Dismissals credited to the bowler
• 3Minutes an incoming batter has

Structural counts taken from the current MCC code. The three-minute limit is the figure in the Laws; international playing conditions set a shorter one.

Ten ways to be out, and the five you will hardly ever see

Bowled, caught, leg before wicket, run out, stumped, hit wicket, obstructing the field, hit the ball twice, timed out, retired out. That is the complete list, and the first five account for almost every wicket ever taken.

Bowled is the purest. The delivery breaks the wicket, and it does not matter what it touched on the way, provided it was not a fielder. Off the inside edge, off the pad and then the stumps, off the shoulder of the bat: still bowled.

Caught takes precedence over everything except a run out. If the ball touched the bat or the glove holding the bat and was caught before it hit the ground, the batter is out caught even if the ball was also going on to demolish the stumps.

Leg before wicket gets its own section, because it deserves one.

Run out is the only dismissal that can happen on any delivery whatsoever, legal or otherwise, and the only common one that can befall a batter who has done nothing wrong beyond trusting a partner.

Stumped is a run out with a specific author. The keeper breaks the wicket while the striker is out of their ground and not attempting a run. The distinction between stumped and run out matters in the scorebook, and it is one of the small readings that a scorecard teaches you to make.

Hit wicket covers the batter who dismantles their own stumps with bat, body or a piece of kit while playing the ball or setting off for a run. It is the rare dismissal that is common enough to see a few times a season.

Then the tail of the list, and the interesting question about it.

Obstructing the field requires wilful interference with the fielding side. Hit the ball twice requires a second strike that is not a lawful defence of the wicket. Timed out requires an appeal against a batter who did not arrive. Retired out requires a batter to leave without the opposing captain's consent.

A reasonable person looks at those four and asks why a code carries laws that fire once a decade. The answer is that a law which is almost never used is not necessarily a dead law. It may be a law that is winning.

Delete the obstruction law and a batter running between the wickets has every incentive to drift into the line of the throw. Delete hit the ball twice and a batter can bat the ball away from an incoming fielder to steal a single. Delete timed out and a side chasing bad light has a free instrument for burning twenty minutes. Each of those tactics disappeared not because players are honourable but because the code made them expensive. The rarity is the evidence of success, which is an unusual thing for a rulebook to be able to claim.

The scorebook splits the ten another way. Bowled, caught, lbw, stumped and hit wicket go to the bowler's figures. Run out, obstructing the field, hit the ball twice, timed out and retired out do not, and a bowler's average is calculated as though those wickets never happened.

What can still get you out on a bad delivery

An unfair delivery does not simply cost the fielding side a run. It also strips away most of the ways they can take a wicket, and the size of that reduction is what makes the no ball worth policing.

Fair delivery8

Wide4

No ball3

Counts of the dismissal methods that can arise from a delivery. Timed out and retired out are excluded throughout, because neither arises from a ball being bowled.

Show the numbers

Dismissals available to the fielding side, by delivery

Item	Methods available
Fair delivery	8
Wide	4
No ball	3

Off a no ball a batter can only be run out, out obstructing the field, or out hitting the ball twice. Not bowled, not caught, not lbw, not stumped, not hit wicket. A bowler who oversteps has, for that delivery, given up on taking a wicket in any of the five ways a bowler is normally credited with.

Off a wide the position is different again: run out, stumped, hit wicket and obstructing the field remain live. A batter charging at a ball sliding down the leg side can still be stumped by a yard, and regularly is.

Lbw is three questions asked in a fixed order

Leg before wicket is the law newcomers find hardest and experienced watchers argue about most, and both reactions come from the same feature. It is a sequence of tests, applied in order, and a decision that fails an early test is over. The umpire does not reach the later questions at all.

The purpose is easy to state. The bowler's target is the wicket. If a batter could stand in front of it and let the ball hit their leg, defending would be trivial and bowling would be pointless. The law exists so that pads cannot be used as a second bat. Everything complicated about it comes from writing that principle down without punishing a batter who was honestly trying to hit the ball.

First, was the delivery legal? A no ball can never produce an lbw. This is checked before anything else because it makes everything else irrelevant, which is exactly what people miss when they see a decision reversed on review for a reason that had nothing to do with the pad.

Second, where did the ball pitch? If it pitched outside the line of leg stump, the batter is not out, and no subsequent fact can rescue the appeal. Not the impact, not the projection, nothing. A ball that pitched in line, or outside off, or did not pitch at all, passes. A full toss cannot pitch anywhere, so it always passes this test, which is why a full toss thumping into the pad in front of leg stump is a live appeal while an identical ball that bounced once outside leg is not.

That asymmetry is the clearest example of the code protecting a principle rather than a result. A ball pitching outside leg has to come back across the batter's own body to reach the stumps, and the batter's body is where it is because that is where a batter stands. Giving them out for it would be punishing them for having legs.

Third, where did it strike the batter? Three cases, and the middle one is the one people garble.

If the impact was between wicket and wicket, in line, the test is passed and it makes no difference whether a shot was offered.

If the impact was outside the line of off stump, the batter survives only if they were genuinely attempting to play the ball. Offer no stroke and you can be given; offer a stroke and you cannot. This is the closest the Laws come to legislating for intent, and it is where the padding-away arguments live.

If the impact was outside the line of leg stump, the batter is not out, full stop, shot or no shot. This is the clause that surprises people who have half-learned the law: they know about pitching outside leg and assume impact outside leg is a matter of degree. It is not.

Fourth, would it have hit the stumps? The ball must be going on to break the wicket. A ball turning past it, swinging past it, bouncing over it, or striking a batter so far down the pitch that it would have died before arriving, is not out.

And running underneath all four, a precedence rule: any contact with the bat, or with the glove holding the bat, before the ball reaches the pad means not out regardless of everything else. The bat comes first.

1. 1Was it a fair delivery?A no ball ends the appeal here. Nothing about the pad, the line or the projection can revive it, because lbw is not available off an illegal ball.
2. 2Did the ball touch the bat first?Any contact with the bat, or the glove holding the bat, before the pad means not out. The bat has precedence over everything that follows.
3. 3Where did the ball pitch?Outside the line of leg stump means not out, whatever happens next. In line, outside off, or no pitch at all, and the appeal survives.
4. 4Where did it strike the batter?In line between wicket and wicket, the appeal survives whether or not a stroke was offered. Outside off, it survives only if no genuine attempt was made to play the ball. Outside leg, it dies.
5. 5Would it have gone on to hit the wicket?Only now does anyone ask about the projection. It must be hitting the stumps, not shaving past them.
6. 6Is the umpire sure?The decision belongs to the umpire on the field. Under review, a projection that is marginal rather than clear leaves that on-field decision standing, which is what umpire's call means.

The tests are applied in order and the sequence stops at the first failure. An appeal that dies at the pitching question is never assessed for whether the ball would have hit.

That last step is where technology enters, and where most of the shouting happens. Ball tracking measures the delivery up to the moment of impact very accurately, then predicts the rest of the path. A prediction carries an error margin, and the margin grows with the length of the extrapolation, so a ball striking the pad on the crease is a far surer projection than one striking a batter half a pitch forward.

Umpire's call is the formal admission of that margin. When the prediction is clear, the technology overturns the umpire. When the prediction only clips the stumps, the uncertainty covers both answers and the honest reading is that nobody can say the umpire was wrong. So the original decision stands, whichever way it went, and two identical replays produce opposite outcomes because the two on-field decisions were opposite. That is not a flaw in the system. It is what "we cannot tell" looks like when a system is obliged to produce a verdict either way. The mechanics of reviews, the tools the third umpire has and the allowance of unsuccessful reviews per innings are worth a separate walk through the review system.

The no ball is six offences wearing one name

Most people think a no ball means the bowler overstepped. Overstepping is only the most visible member of a family, and the others catch out even experienced viewers.

The front foot. Some part of the front foot, grounded or raised, must be behind the popping crease when it lands. Two things follow. The foot may hang in the air over the line as long as part of it is behind the line, which is why a bowler whose toe overhangs is not automatically illegal. And the judgement is made at the instant of landing, not where the boot finishes after it slides, which is why the freeze frame used on television is a specific frame rather than the clearest one.

The back foot. It must land inside the return crease and not touching it. This one is called less often, and it is the reason a bowler drifting wide of the crease for an angle can find themselves called without going anywhere near the front line.

Height. A delivery that reaches the striker above waist height without bouncing is a no ball. The measurement is the striker's waist while standing upright at the popping crease, which means a batter who has charged three paces down the pitch and been met by a waist-high full toss where they now stand has not necessarily been bowled a no ball. The law is measured against where a batter is entitled to stand, not where they chose to go.

Short-pitched bowling. The code limits how many fast short deliveries passing above shoulder height a bowler may send down in an over, and competitions set their own counts, which are more generous in Test cricket than in Twenty20. Exceed the limit and it is a no ball. A bouncer that passes clean over the striker's head is dealt with differently, and under the Laws it is called a wide rather than a no ball, which surprises almost everybody.

The action. Straightening the arm through the delivery swing beyond the permitted tolerance is a throw, and a throw is a no ball. So is bowling underarm without prior agreement, a prohibition that exists because underarm was once used to make the final delivery of a limited-overs match impossible to hit for six. So is switching from over the wicket to round it, or from right arm to left, without telling the umpire, because the batter is entitled to know what is coming.

The field, and the pitch itself. More than two fielders behind square on the leg side is a no ball, a restriction with an obvious ancestor in the leg theory of the 1930s. So is a fielder encroaching on the pitch before the ball reaches the striker, and a wicketkeeper who is not wholly behind the stumps when the ball arrives. In limited-overs cricket the fielding restrictions themselves are enforced by no ball, so a captain who leaves an extra man outside the ring during a restricted phase of the innings concedes the run and the extra ball automatically.

A ball that bounces more than once before reaching the popping crease, or that comes to rest in front of the striker, is also a no ball, because a delivery the batter cannot address in any normal way is not really a delivery.

The thread through all of it is the same. Each of these is a way of taking an advantage the batter cannot counter, and the law never asks whether the advantage was taken deliberately, because the batter's disadvantage is identical either way.

A no ball costs one penalty run, an extra delivery, and immunity for the batter from every dismissal except the three listed earlier. Which is not much, and that is precisely the problem the next rule was invented to solve.

The free hit made the no ball expensive

One run and one extra ball is a trivial price in a format where the total runs to three hundred. Front-foot no balls were quietly being treated by fast bowlers as an acceptable cost of bowling at full tilt, since the delivery that overstepped might still take a wicket the batter would not otherwise have survived, and the penalty was a rounding error.

The free hit changed the arithmetic. The next legal delivery becomes one on which the batter can only be dismissed in the same three ways available off the no ball itself. The expected cost of overstepping went from about one run to several, and the frequency of front-foot no balls fell.

Some details catch people out. The field may not be rearranged for a free hit unless the batters crossed, which stops a captain from packing the boundary in response. A free hit is not a free ball, and batters are run out on them. If the free hit delivery is itself a no ball, the free hit rolls over to the next legal delivery. And because the batter cannot be bowled, a ball that cannons into the stumps on a free hit ends nothing at all: the ball stays live and the batters can and do run.

Note where this rule lives. The free hit is not in the code kept at Lord's. It is a playing condition, written by the competition, which is why it applies to an international white-ball match and does not automatically apply to your Saturday league.

Why a wide means one thing in a Test and another in a T20

A wide is a delivery the batter could not hit with a normal cricket stroke from where they are standing. It costs a penalty run and an extra ball, and it is judged on a two-part test: the ball must have passed out of reach of the striker where they actually were, and also out of reach of a striker standing in a normal guard position.

The second limb is the anti-manufacturing clause. Without it, a batter could shuffle two feet across their stumps after the bowler let go and convert a decent delivery into an extra. Umpires judge the striker's position from the point at which the bowler is committed, not from wherever the batter has wandered to by the time the ball arrives.

Now the part people find inconsistent, which is deliberate rather than sloppy. In Test cricket a ball passing outside off stump is very rarely called wide. In white-ball cricket, where the popping crease carries painted guide markings, the same ball frequently is. Down the leg side the standard is strict in every format.

The reason is economic, not aesthetic. In a Test the bowler has unlimited deliveries and the batter is entitled to leave the ball alone, so bowling wide of off stump gains the bowler nothing: the batter simply does not play, the ball threatens nothing, and the contest carries on. In a limited-overs innings the deliveries are the scarce resource. A bowler who sends down six unhittable balls has denied the batting side six scoring opportunities, and unless the wide is policed tightly, bowling nowhere near the batter becomes a viable death-overs tactic. The strict white-ball wide exists to make wasting a ball cost a ball.

Two further points. A delivery that touches the bat or any part of the batter is never a wide. And a wide can still produce a wicket, in the four ways set out earlier, which is why a keeper standing up to the stumps stays interested in a ball sliding down the leg side.

What a fielding side may lawfully do to the ball

Strip away the scandals and the law here is short, clear and almost entirely permissive about the things that actually matter for bowling.

A fielding side may polish the ball on clothing, provided no artificial substance is involved. It may dry a wet ball with a towel, and it may have mud removed, both under the supervision of an umpire. That is the whole list of permitted interventions, and it is enough to run the entire craft of ball management: shine one side, let the other roughen naturally, and the difference between the two is what makes a ball move sideways. Every conventional swing bowler and every practitioner of the older, rougher art of reverse swing works within those three permissions.

What is prohibited is anything else done to change the condition of the ball. Rubbing it on the ground. Scratching it with a fingernail or any object. Lifting or picking at the seam. Applying any artificial substance, a category which under the current code includes saliva, previously the most ordinary thing in the game and now simply not allowed.

The sanction is procedural rather than dramatic, and it runs in a set order.

1. 1The umpires inspect the ballEither umpire may examine the ball at any time. The judgement is on the condition of the ball, not on catching somebody in the act.
2. 2The ball is changedIf the umpires decide the condition has been unfairly altered, the ball is replaced with one they consider to be in a comparable state of wear. The batting side, not the fielding side, has the say in choosing it.
3. 3Five penalty runs to the batting sideThe award is immediate and does not depend on identifying who did it. Penalty runs go into the total as extras and are charged to no bowler.
4. 4The fielding captain is told, and the offence is reportedThe umpires inform the captain that the ball has been changed and why, and report the matter after the match to whoever governs the competition.
5. 5The competition takes it from thereSuspensions and fines are not in the Laws. They come from the disciplinary code of the body running the match, which is why identical acts attract different punishments in different competitions.

The sequence set out in the Laws. Competitions add their own disciplinary process on top, run by a match referee, which is where suspensions come from.

Two things are worth noticing about that sequence. The penalty is awarded to the batting side rather than deducted from the bowling side, which sounds identical and is not: penalty runs land in the score immediately and can decide a close chase. And the umpires are ruling on the ball, not on a person. They do not need to establish who did what to it.

Obstruction, handled ball, and the dismissal that changed address

A batter is out obstructing the field if they wilfully obstruct or distract the fielding side by word or action while the ball is in play. It is rare and it is uncomfortable, because unlike every other dismissal it requires an umpire to make a finding about intent.

The current code folded the old separate dismissal of handled the ball into this one. Deliberately striking the ball with a hand that is not holding the bat is now a form of obstruction, with an exception for a batter acting to avoid injury. So is returning the ball to a fielder without being asked, which sounds like a courtesy and is in fact an interference with a live ball.

Two boundaries matter in practice. A batter running between the wickets may take whatever line they like, and changing course is not automatically an offence. What is an offence is moving into the path of a throw with no purpose other than to stop it arriving. Umpires look for a movement that makes no sense as running and every sense as blocking.

And hitting the ball twice is a different law. A batter may lawfully strike the ball a second time for one reason only, to defend their wicket, and may not score from that second strike except from an overthrow. Patting a ball away from the base of the stumps is fine. Batting it away from an approaching fielder to steal a single is not.

Then there is the run out of a non-striker who leaves their ground before the ball is released. The bowler may break the wicket from the moment the ball comes into play until the instant they would normally have been expected to release it, and the batter is out run out.

The interesting thing about this law is not its content but its address. It used to sit inside the unfair play law, alongside deliberate distraction and altering the condition of the ball. In the current code it sits under run out, with the other run outs.

That relocation was an argument, made in the layout of a document. A non-striker who leaves early is stealing distance in a race they are about to run, and the only remedy available to the fielding side is this one. Filing the dismissal under unfair play implied that the bowler taking that remedy was the party behaving badly, and the reclassification says plainly that they are not. Whether it settled the argument in the pavilion is another matter. What it did settle is where the law lives, and a code that publishes its own reasoning does not move a clause between chapters by accident.

Timed out, retired out, and who else is allowed on the field

Timed out requires an incoming batter to be ready to receive the next delivery, or for their partner to receive it, within three minutes of the fall of the previous wicket. International playing conditions cut that period down considerably. If the batter is not ready and the fielding side appeals, the batter is out without facing a ball.

The dismissal is disliked, and the objection is genuinely reasonable: a broken strap and a deliberate stall look identical from the boundary, so the law punishes both. The defence is that cricket has no clock to run down and no other mechanism against delay, and a game that cannot police arrival can be stalled by whichever side benefits from stalling.

Retired hurt and retired out are two different things separated by consent. A batter who leaves the field because of injury or illness is retired hurt, may resume the innings at the fall of a later wicket or at the end of it, and is recorded as retired not out if they never come back. Nobody is credited with a wicket. A batter who retires for any other reason without the consent of the opposing captain is retired out, may not return unless that captain agrees, and the innings counts as a dismissal, though again no bowler gets it.

Retired out was a dead letter for most of the game's history. Twenty-over cricket revived it as a tactic: a set batter struggling against a particular kind of bowling, or simply out of energy in the last few overs, can be swapped for a fresh striker better suited to the moment. It is legal, it is rational, and it still causes a fuss, mostly because a batter walking off unbeaten offends an instinct much older than the format.

Substitutes are tightly bounded. A substitute may field. They may not bat, may not bowl, and may not act as captain, and under the current code they may keep wicket only if the umpires consent. The logic is a clean division: fielding is a shared burden that any eleven bodies can carry, while batting and bowling are the contest itself, and replacing a participant in the contest would change the contest. The current code also has no provision at all for a runner, following the international game, which stopped allowing them some years earlier.

Concussion replacements are the exception, and they are not in the Laws. They are a playing condition, adopted because the alternative was a system that rewarded a concussed player for staying on. A replacement must be approved by the match referee and must be like for like, meaning the substitute should not give the side an advantage over the player they replace, and once approved that replacement can bat and bowl exactly like anyone else. It is the clearest case in modern cricket of player welfare overriding a structural principle that had stood for two centuries.

Dead ball ends more arguments than any other law

The ball is dead when it is finally settled in the hands of the bowler or the wicketkeeper, when it reaches the boundary, when a batter is dismissed, when it lodges in a batter's clothing or equipment, when penalty runs are awarded, at the call of over or time, and in a further list of defined circumstances. While the ball is dead nothing can happen: no runs, no dismissals, no appeal worth making.

That sounds like housekeeping. It is the most load-bearing law in the code.

Almost every disputed passage of play resolves into a single question about timing. Did the batters complete the run before the ball was dead, or after? Was the ball still live when it ricocheted off the keeper's gloves to the boundary, making those overthrows legitimate? Had the ball settled in the fielder's hands before the batter wandered out of their crease? Was the bail already off? Once you know the moment the ball became dead, the rest is arithmetic.

The umpires may also call dead ball at their discretion, and the list of reasons is deliberately open ended: a serious injury, a batter distracted or unsighted, an intervention by someone not part of the match, a delivery the umpire judges the batter was not ready to receive. The most common use is the one nobody notices, when a batter pulls away because a sightscreen has moved or a spectator has walked behind the bowler's arm, and the umpire quietly wipes the delivery out of existence.

That open-endedness is intentional. Cricket is played for many hours in open public spaces, and no code could enumerate everything that might interrupt a delivery. Dead ball is the general-purpose reset that lets the umpires deal with all of it without needing a clause for each case.

Its edge cases are among the most disputed things in the sport, because the call can erase a boundary or a wicket that everybody in the ground has already seen happen, and there is no appeal against it. It is also one of the signals worth learning to read, since the umpire crossing and uncrossing the wrists below the waist is often the first indication that what you just watched did not count. The full vocabulary of what the umpire's arms are telling you is more useful than it sounds, particularly at grounds where nothing is announced.

One related oddity, since it comes up: if the ball strikes a fielding side's helmet that has been left on the ground behind the keeper, five penalty runs go to the batting side. The ball is dead, the runs stand, and it is the only situation in cricket where a piece of unattended equipment costs a team five runs.

The spirit of cricket, and the honest argument against it

The code opens with a Preamble on the Spirit of Cricket. It states that the game owes much of its appeal to being played not only within its laws but within their spirit, it places responsibility for that on the captains, and it names what falls outside it: disputing an umpire's decision, abusing an opponent, cheating, directing violence at anybody in or around the game.

The obvious question is what a passage like that is doing in a rulebook. A rule that cannot be enforced is not a rule, and for most of its life the Preamble genuinely could not be enforced. It was a statement of values sitting at the front of a legal document.

That changed when the current code added a players' conduct law with real teeth. Offences are graded across four levels, and the sanctions escalate from a warning, to five penalty runs to the opposition, to removing the offending player from the field for a period, to removing them for the rest of the match. Umpires can now do something about behaviour, on the field, immediately, without waiting for a hearing.

The argument against the Preamble is worth stating properly, because it is not simply grumbling. It is that "the spirit of the game" has repeatedly been used not to restrain bad behaviour but to shame players for using laws they were fully entitled to use. The run out of a backing-up non-striker is the standard case: for decades the bowler who took a wicket exactly as the code allowed was the one asked to explain themselves, while the batter stealing metres was not. A clause vague enough to mean anything tends, in practice, to mean whatever the more established party wants it to mean. There is also a fair charge that the phrase carries a set of cultural assumptions about who plays the game properly, assumptions that have not aged gracefully.

The argument for it is that cricket is unusually dependent on self-policing. Two umpires cannot see everything across five days, batters have historically been expected to walk for edges nobody else detected, and captains hold powers no other sport hands to a player. A code governing a game like that benefits from stating out loud what it is trying to protect, and the four-level conduct law means the statement is no longer decorative.

Both things are true. The Preamble is the most criticised page in the code and it is also the reason an umpire has any vocabulary at all for a situation the specific laws did not anticipate.

Who owns the laws, and who writes what you are actually watching

This is the distinction that resolves most arguments in a pub, and hardly anybody makes it.

MCC owns the Laws. It is the custodian, it consults widely, and it alone can amend the code. Those forty-two laws govern cricket everywhere, from a Test match to a school field, and they are published in full and free to read.

Nobody plays a televised international purely under them.

Every competition writes playing conditions that sit on top of the code and modify it. The ICC writes them for international cricket. National boards write them for their domestic competitions. Franchise leagues write their own. A playing condition can change a threshold, add a procedure, or suspend a law outright, and it applies only to that competition.

The list of things that are playing conditions rather than laws is longer than most people expect. The Decision Review System is one. The free hit is another. Powerplays and fielding restrictions, over-rate penalties, the number of bouncers permitted per over, the Super Over used to settle a tie, concussion replacements, the pink ball and the timings of a day-night Test, the third umpire calling front-foot no balls from the box rather than leaving them to the standing umpire: all playing conditions. So is the rain-affected target calculation that decides so many limited-overs matches, which is a mathematical method adopted by competitions, not a law of the game.

Playing conditions also move faster than the code, because they can. A competition can drop a procedure between seasons if it stops working, as the ICC did with the soft signal, which required the on-field umpires to give a provisional decision before referring a disputed catch upstairs. The Laws themselves change rarely and deliberately, on a cycle measured in years, precisely so that the version played in a village on Sunday remains recognisably the same game as the one on television.

So when a commentator says "that is not in the laws", they are often right and it does not matter, because the match in front of them is being played under a document with a different name. And when somebody at a club ground insists on a rule they saw on television, the correct question is which competition's playing conditions they got it from.

Where a fielder may stand is a neat illustration of the split. The core restrictions, no more than two behind square on the leg side and no fielder on the pitch before the ball arrives, come from the Laws and apply to everybody. The circle, the powerplay counts and the number of players permitted outside it come from playing conditions and change format by format, which is why the names and geometry of fielding positions stay constant while the legal arrangement of them does not.

The cricket laws that actually decide matches

Most of the code will never affect anything you watch. A handful of it decides nearly everything, and if you learn only these, you will follow the game better than most people in the ground.

The lbw sequence, in order. Legal delivery, bat first, pitching, impact, projection. Almost every argument about an lbw decision is really two people applying the tests in different orders, or one of them assuming the projection is the only question.

The front-foot line, and what follows it in white-ball cricket. A no ball is a run, a ball, and in limited overs a free hit. The three together turn a foot fault into a passage of play, which is why bowlers under pressure look down at the crease between deliveries.

The wide, judged by format. The same delivery is a legitimate probing line in a Test and an extra in a Twenty20, and knowing which standard is in force tells you what the bowler is allowed to try.

The moment the ball goes dead. Every dispute about overthrows, completed runs, a batter out of their ground, or a wicket that came a fraction late, is a dispute about this and nothing else.

The grounding of the bat in a run out. The bat or some part of the batter must be grounded behind the popping crease, and a bat that has bounced up off the ground as the batter dives is not grounded at all. More run outs turn on this than on the quality of the throw.

Learn those five and the rest of the code becomes what it was written to be: a long, patient record of every way somebody once found to make the contest unfair, and what was done about it. The wider set of explainers on the game is collected in the cricket section, and every law above is easier to hold on to once you stop reading it as a rule and start reading it as an answer.