No. A ball becoming dead ends that delivery’s play, but it does not automatically end the over. In an ordinary case, the completed delivery remains part of the over, and the bowler may begin the next delivery. Deciding whether the over is complete requires its valid-ball count as well as the ball’s state. Other dead-ball cases and umpire-counting provisions are outside this comparison.
What the dead-ball moment records
The important distinction is between the state of the ball and the count of the over. Under MCC Law 20 on Dead ball, play becomes dead at the relevant stopping point, while “Over” or “Time” cannot be called until the ball is dead. The ball can come into play again when the bowler starts the next run-up or delivery action.
Hypothetical: an ordinary first delivery
Example: The bowler delivers the first valid ball of an over. The batter completes ordinary play without a dismissal or special event. The ball travels to the wicketkeeper, who gathers it and the play is then settled as dead.
| Record | Output |
|---|---|
| Delivery status | Dead after completed play |
| Valid-ball count | 1 of the over |
| Over status | Not finished |
| Next action | Prepare for the next delivery |
The evidence in this example is the delivery record itself: it was valid and completed before the ball became dead. “Dead” therefore closes that play, but it does not erase the valid-ball entry or convert the over into a completed over.
Contrast: dead after the last valid delivery
If the same kind of settled dead-ball moment occurs after the final required valid delivery, the result is different. The ball is dead, and the over may then be called complete. The decisive fact is not simply that the ball is dead; it is whether the over’s valid-ball requirement had already been met.
This explanation covers the ordinary hypothetical above. Extraordinary dead-ball situations can have separate consequences, so this example should not be used to claim that every dead ball counts as a valid delivery.