Chapter 98: RCB vs. Delhi Capitals – The Next Battle - Cricket System:Second Chance For Raj - NovelsTime

Cricket System:Second Chance For Raj

Chapter 98: RCB vs. Delhi Capitals – The Next Battle

Author: PavanRaj143
updatedAt: 2025-07-13

CHAPTER 98: RCB VS. DELHI CAPITALS – THE NEXT BATTLE

After their disciplined and well-executed chase against Punjab Kings, RCB was now shifting their focus to their next challenge—Delhi Capitals, a team that had built a reputation for fierce pace attacks and calculated batting phases.

Raj sat in the strategy room, studying Delhi’s key players and recent performances. Unlike Punjab, who relied on explosive batting bursts, Delhi was more structured, ensuring stability in the powerplay before gradually accelerating in the death overs.

"We won against aggression last match. Now, we counter precision."

RCB’s preparation would require an approach centered on adaptability, controlled aggression, and structured field placements to dismantle Delhi’s batting rhythm.

The players gathered for their final tactical briefing, fine-tuning their plans for yet another high-intensity encounter. The match was about to begin.

Delhi Capitals had a well-balanced playing style, unlike teams that relied on singular strengths. Their key strategies revolved around:

Powerplay Stability Before Acceleration – Their openers didn’t take unnecessary risks early, ensuring they built a foundation for middle-over hitters.

Middle-Order Anchoring Before Late-Game Attack – With players like Rishabh Pant and Mitchell Marsh, Delhi could rebuild effectively if early wickets fell.

Bowling Adaptability Based on Conditions – Instead of enforcing a rigid bowling strategy, Delhi adjusted based on pitch behavior and opposition weaknesses.

RCB had studied every detail, ensuring they could break Delhi’s rhythm before their acceleration phases.

Raj outlined the key elements of RCB’s plan for neutralizing Delhi’s structured approach.

Early wickets in the powerplay – Unlike Punjab, Delhi wasn’t reckless in the first six overs. RCB needed to force mistakes instead of waiting for them.

Spin-dominant middle overs – Delhi’s batters thrived against pace but had certain vulnerabilities against spin rotations.

Controlled acceleration in the chase – If RCB had to chase, they had to pace their innings perfectly, ensuring they didn’t get trapped into late-game desperation.

The toss was about to take place. Raj tightened his gloves, mentally preparing himself for another test of execution and adaptability.

The players took their positions as Delhi’s openers, David Warner and Prithvi Shaw, walked onto the pitch. The tension was unmistakable—both teams had studied each other’s weaknesses extensively, knowing that early control would define the outcome of this battle.

Raj adjusted his gloves, standing near the field boundary, scanning the conditions. The pitch had a subtle hint of lateral movement, something RCB’s pacers could exploit.

Delhi’s batting philosophy revolved around steady powerplay scoring before launching their acceleration phase later, meaning the opening overs required RCB to create early breakthroughs and disrupt their foundation-building phase.

The umpire signaled readiness, and Siraj stepped up to open the attack. The game was officially in motion.

Unlike Punjab’s reckless hitting, Delhi’s openers were known for methodical aggression, balancing caution with calculated shots. Their powerplay game plan relied on:

Controlled hitting rather than blind power – Warner and Shaw would target gaps rather than attempt early sixes.

Utilizing crease depth to adjust for swing movement – Delhi’s batters had trained specifically for late ball movement, ensuring they didn’t get trapped by swing-heavy deliveries.

Boundary bursts between overs 3-6 – Instead of hitting early, Delhi preferred pushing aggressively after testing the pitch conditions.

Raj signaled to Siraj. RCB’s response needed precision.

Siraj sprinted in, delivering a full-length, angling-out delivery to Warner.

Warner judged the movement instantly, adjusting his stance and pushing the ball toward deep point.

Single taken.

Delhi wasn’t rushing, but their batters were finding gaps immediately, avoiding any dot-ball pressure.

Next ball—sharp bounce, forcing Shaw onto the back foot.

Shaw hesitated slightly, tapping the ball toward mid-off.

Dot ball.

RCB had successfully stalled Shaw for the moment, but Warner was reading the bowling patterns quickly.

The third over arrived, and Delhi started increasing their intent, using their initial reading of the pitch to dictate their scoring bursts.

Delhi executed their planned approach perfectly—after two overs of stable singles, they targeted boundary bursts from over four onwards.

First ball—Siraj bowled a tight off-stump delivery, expecting another controlled shot.

Warner stepped forward aggressively and lofted it past extra cover.

Four runs.

RCB’s fielders adjusted immediately, cutting off his angles.

Next ball—wide ball outside off, forcing Shaw to reach.

Instead of driving, Shaw timed a well-placed shot between point and third man.

Four runs.

Delhi had officially entered their powerplay scoring phase.

Score Update – Delhi’s Powerplay Performance

Delhi Capitals – 58 for no loss (6 overs)

David Warner – 29*(19), 3 fours

Prithvi Shaw – 26*(17), 2 fours, 1 six

Delhi had executed their opening plan efficiently, ensuring a stable foundation for their middle order.

Raj observed carefully, signaling to his spinners. The next phase required RCB to counter their smooth progression.

As the powerplay ended, Delhi stood at 58 for 0 after six overs, their openers having successfully built a solid foundation. But now, with the field spreading, they had to navigate RCB’s spin-dominant middle overs, where Raj had planned for maximum containment.

Delhi wasn’t a reckless batting unit—they played with precision. That meant they wouldn’t simply attack RCB’s spinners outright. Instead, they would try to rotate strike, control run flow, and gradually build toward their acceleration phase later.

Raj observed carefully from the boundary, noting how the Delhi captain gestured toward his batters before the start of the seventh over. He knew that moment—it was a clear signal: "Settle in, adapt to spin, don’t take unnecessary risks."

"Let’s see how long they can hold off under pressure."

The next battle was about to unfold.

RCB’s Spin Strategy – Breaking Delhi’s Rhythm

RCB’s middle-over tactics revolved around structured bowling rotations, ensuring Delhi’s batters never settled against one particular bowler. Their spin setup included:

Early spin introduction before Delhi adjusts – Instead of waiting until over 10, RCB was bringing in spin immediately after the powerplay.

Defensive fields forcing Delhi into calculated placements – Cutting off Delhi’s favored run-scoring angles.

Variation in bowling speeds – Preventing Delhi’s middle order from reading delivery patterns too easily.

Maxwell marked his run-up, ready to execute the plan.

Maxwell fired in the first ball—flatter trajectory, drifting toward off-stump.

Warner adjusted quickly, stepping back and guiding the ball toward deep point.

Single taken.

Delhi wasn’t forcing anything, but their batters were ensuring movement every ball.

Next ball—slower flight, inviting an attacking shot.

Shaw hesitated, deciding against a lofted stroke, instead placing the ball toward mid-wicket for a single.

RCB had stalled Delhi’s natural aggression, but the opposition was keeping their run rate from dropping too much.

By over 10, Delhi had adjusted entirely to a low-risk batting phase. But Raj knew this was exactly where RCB could tighten control even further.

Spin angles widened to push Delhi into off-side play – Forcing them away from their stronger leg-side strokes.

Deep square-leg reinforcement to trap mistimed sweeps – Preventing Delhi from using their late cuts effectively.

Bowler endurance testing – Making Delhi’s batters face extended spin spells before pace returned.

RCB was dictating the chase target, ensuring Delhi didn’t accelerate yet.

Delhi realized their scoring rate had dropped, and they couldn’t afford to delay acceleration much longer. Their captain signaled his batters—"We push now."

RCB’s bowlers remained composed.

The first ball of over 13 arrived—sharp turn, angling inward.

Shaw attempted a flick toward deep mid-wicket.

Caught at the boundary. OUT!

RCB had their breakthrough, immediately slowing Delhi’s push.

Raj exhaled slightly.

"One gone. Now we squeeze tighter."

Score Update – Delhi’s Position Before the Death Overs

Delhi Capitals – 112 for 1 (15 overs)

David Warner – 58*(42), 6 fours

Prithvi Shaw (out) – 47 (34), 4 fours, 1 six

New batter in – Rishabh Pant

Delhi had maintained stability, but now their middle order had to play under increased pressure.

RCB held control, but the final overs would decide the match outcome.

The match had reached its decisive phase. Delhi stood at 112 for 1 after 15 overs, their innings stabilizing but yet to fully accelerate. With only five overs remaining, their ability to push the total past the 180 mark depended on how well Rishabh Pant and David Warner handled RCB’s pace attack.

Raj observed closely from the boundary, noting the shift in Delhi’s approach. They had played patiently against spin, but now, with pace returning, they were preparing for an explosive finish. Pant was known for taking risks early, and Warner would ensure stability while attacking specific deliveries.

"They want controlled acceleration. We can disrupt that."

Hazlewood took his mark for the 16th over, knowing the next five overs would decide the chase target.

Delhi wasn’t blindly attacking—they had a structured plan for the last five overs. Their approach revolved around:

Targeting pace instead of spin – Now that RCB had switched back to fast bowling, Delhi was waiting for full deliveries to launch their power phase.

Picking overs 16, 18, and 20 for aggression – Instead of swinging every ball, they structured their attack for specific moments.

Avoiding aerial risks before the final three overs – Delhi knew RCB’s fielders were positioned for boundary traps, meaning they couldn’t afford early mistakes.

Raj signaled toward Hazlewood. "We keep them under 180. That’s the goal."

Hazlewood sprinted in, delivering a sharp, full-length ball angling toward off-stump.

Pant stepped forward instantly, slicing it between point and third man.

Four runs.

RCB adjusted their field placements—Delhi had officially begun their late scoring phase.

Next ball—short-pitched, bouncing toward Warner’s ribs.

Warner didn’t hesitate—he pulled aggressively toward fine leg.

Four runs.

Delhi was shifting gears, but RCB’s bowlers remained disciplined, preventing consecutive sixes.

Siraj stepped in for the 19th over, knowing Delhi was fully committed to acceleration now.

First ball—wide yorker, forcing Pant to reach for it.

Pant stretched forward but misjudged the timing.

Edge taken. Caught behind. OUT!

RCB had removed Delhi’s biggest late-game threat.

Raj exhaled, adjusting his gloves.

"That disrupts their rhythm. We control the final over now."

Final Score – Delhi’s Total Before RCB’s Chase Begins

Delhi Capitals – 181 for 4 (20 overs)

David Warner – 79 (52), 8 fours

Rishabh Pant (out) – 36 (20), 4 fours, 1 six

RCB successfully limits Delhi’s acceleration in the final overs

Raj turned toward the dugout, scanning the scoreboard.

"181. Manageable. Now, we chase."

To be continued....

Novel