Rain was a significant presence throughout the game in Napier, interspersing the second half of New Zealand’s innings at different junctures. At 17.5 overs, heavy rain forced the abandonment of the hosts’ innings, with their score at 173-5.

According to ESPNcricinfo’s ball-by-ball commentary, Bangladesh’s would have been set 179 to win, had the game been reduced to 17 overs. However, it appeared that Bangladesh were under the impression they were chasing 148 in 16 overs [the same figure appeared on the Blackcaps’ Twitter handle], even though, according to the commentary, the DLS 4.0 sheet revealed it to be 171 in 16 overs.

Bangladesh knew they were chasing 148 in 16 overs. https://t.co/jTpyHy2H3E

— Mohammad Isam (@Isam84) March 30, 2021

The confusion extended further when Bangladesh began their innings without any official announcement of the revised total. After bowling a whole over and three deliveries, play was paused when the umpires realised that Bangladesh were playing without a target. At the end of the first over, ESPNCricinfo‘s commentary stated Bangladesh to be 6-0, with 143 needed off 90 balls, which would have made their target 149.

Play was suspended as officials, led by match referee Jeff Crowe, scrambled to get their calculators out while the players took an unplanned drinks break. The Bangladesh team manager was seen entering the match referee’s room. After a brief delay, the match officials finally released the revised target, which came out as 170 in 16 overs. After the 13th over of the Bangladesh innings, the target was again revised t0 171 – the total initially predicted by ESPNCricinfo.

New Zealand all-rounder Jimmy Neesham, not part of the T20I squad, tweeted: “How is it possible to start a run chase without knowing what you’re chasing? Crazy stuff. #NZvBAN”.

For an action-packed game that had all the elements of a classic, it’s the DLS system that ended up being the most talked-about aspect.