• Welcome to the Cricket Web forums, one of the biggest forums in the world dedicated to cricket.

    You are currently viewing our boards as a guest which gives you limited access to view most discussions and access our other features. By joining our free community you will have access to post topics, respond to polls, upload content and access many other special features. Registration is fast, simple and absolutely free so please, join the Cricket Web community today!

    If you have any problems with the registration process or your account login, please contact us.

Stumped!

ataraxia

International Coach
ataraXIa is sad to announce the departure of veteran all-rounder Michael Winton. He will finish as the club's 5th most capped player, 3rd highest run scorer, and 5th leading wicket-taker.

Noted as a consistent if sometimes slow top-order 50-over bat, the former Moooo player is more well-known for his exploits in T20s, with countless stable efforts gluing the innings together and providing excellent left-hand foil for rampaging right-handed hitters. As a bowler his quality was first seen as questionable, but he blossomed to the point where he was bowling a full quota in both formats, and if the pitch was sufficiently dry there was little drop off in quality at all to him from the specialist bowlers. At times his efforts as an Economical bowler, opening the bowling in 50-over cricket and bowling through the middle in T20s, belied his low skill. The former Moooo player has left an indelible impression on the club in his time as its primary all-rounder and will be sorely missed.

Management has decided the time has come to move on from Winton, but he will leave the club as its greatest all-rounder. The 28-year-old has been replaced by Agam Naidoo, a better bowler but worse bat, who will fulfill a caretaker role while young batting all-rounders Vedanga Roopak and Tharaka Sellamuttu develop. It is hoped that in his last competitive act for the club, in the Cup, he will see the team through to round 5.
 

SillyCowCorner1

Request Your Custom Title Now!
ataraXIa is sad to announce the departure of veteran all-rounder Michael Winton. He will finish as the club's 5th most capped player, 3rd highest run scorer, and 5th leading wicket-taker.

Noted as a consistent if sometimes slow top-order 50-over bat, the former Moooo player is more well-known for his exploits in T20s, with countless stable efforts gluing the innings together and providing excellent left-hand foil for rampaging right-handed hitters. As a bowler his quality was first seen as questionable, but he blossomed to the point where he was bowling a full quota in both formats, and if the pitch was sufficiently dry there was little drop off in quality at all to him from the specialist bowlers. At times his efforts as an Economical bowler, opening the bowling in 50-over cricket and bowling through the middle in T20s, belied his low skill. The former Moooo player has left an indelible impression on the club in his time as its primary all-rounder and will be sorely missed.

Management has decided the time has come to move on from Winton, but he will leave the club as its greatest all-rounder. The 28-year-old has been replaced by Agam Naidoo, a better bowler but worse bat, who will fulfill a caretaker role while young batting all-rounders Vedanga Roopak and Tharaka Sellamuttu develop. It is hoped that in his last competitive act for the club, in the Cup, he will see the team through to round 5.
What a player. We are proud to have had a player of this caliber in our set-up. I remember when I let him go into the market and you picked him up. He is a very reliable player and does the job required. Not a superstar by any stretch of the imagination.

I also wish Naidoo all the best as part of your team's journey to the pinnacle of Stumped!
 

cnerd123

likes this
We're halfway through the season!

ZCC have really struggled in the 50 over format this season. An upset defeat to get knocked out of the Cup in R2, and are dead last in Div 1.1, with just the solitary win to show for it.

The batting has not fired at all - Ahsan and Samra have had good seasons so far, while Younis is doing decently. Raun Shkorer has averaged just 15 in 9 competitive 50 over innings, and the rest of the lineup has hardly fared much better. Ahsan has also been our best bowler, and young Naeem Ashraf has gone alright when playing on dry tracks, but the rest of the attack has struggled.

The gap in quality between us and the rest of the teams has been clear to see - we're in the bottom 3 of XPV alongside Krypto Knights (who we beat) and Basco (who beat us when we failed to chase just 209 to win).

I think the reason we've struggled so much to stay competitive is a lack of a clear winning strategy. We have been unable to make our home pitch a 'fortress'. While the versatility in our squad was our strength in Div 2, it has just meant that we are mediocre over a wide range of conditions in Div 1.

With no clear strategy on how to arrest this slide in sigh, a drop back to Div 2 seems likely. ZCC management is contemplating when to consider the rest of the Div 1 season a wash and to use the game time to develop some upcoming talent instead. There are also talks of scouting the TM, but indecision over what gaps really need filling. With CWC10 looming, some decisions will need to be made and made quickly.

What complicates this situation is that ZCC have been exceptional in the T20 format, and are in 2nd place in Div 1.1 on NRR! Of course, things can change quickly in this volatile format, but one hopes this strong start will ensure another season in the top flight. Raun has found the shorter format more to his speed, averaging 59 at a SR of 124, while Sampath and Ghani have taken 28 wickets between them in 7 games. The same personnel that have struggled in the 50 over have done excellently so far in the T20, so any changes will need to consider the repercussions in the shorter format. Danial Ahsan has been excellent in this format too, with the 2nd most runs and 3rd most wickets - is a call up to the BD Nat squad on his radar?

The Dev side have more or less performed to expectations - bot bashing in Div 3 but bottom half of the table in CWC9. Ewen Rockall and Naeem Ashraf will age out of the side in 6 and 10 weeks respectively, so the hunt is on for their replacement, while tough decisions are being made about their future in the squad. Rumours have it that frontline spinner Tim Chester - with just 10 wickets in 12 competitive games this season - might be cut to make room for the young bowlers.

Financially ZCC have managed to earn close to 600k over the course of the season. This represents around 25% of ZCC's pre-season bank balance. However, with just 2.8 mill in the bank overall, ZCC are not in a position to make any major purchases for world class players.
 
Last edited:

SillyCowCorner1

Request Your Custom Title Now!
We're halfway through the season!

ZCC have really struggled in the 50 over format this season. An upset defeat to get knocked out of the Cup in R2, and are dead last in Div 1.1, with just the solitary win to show for it.

The batting has not fired at all - Ahsan and Samra have had good seasons so far, while Younis is doing decently. Raun Shkorer has averaged just 15 in 9 competitive 50 over innings, and the rest of the lineup has hardly fared much better. Ahsan has also been our best bowler, and young Naeem Ashraf has gone alright when playing on dry tracks, but the rest of the attack has struggled.

The gap in quality between us and the rest of the teams has been clear to see - we're in the bottom 3 of XPV alongside Krypto Knights (who we beat) and Basco (who beat us when we failed to chase just 209 to win).

I think the reason we've struggled so much to stay competitive is a lack of a clear winning strategy. We have been unable to make our home pitch a 'fortress'. While the versatility in our squad was our strength in Div 2, it has just meant that we are mediocre over a wide range of conditions in Div 1.

With no clear strategy on how to arrest this slide in sigh, a drop back to Div 2 seems likely. ZCC management is contemplating when to consider the rest of the Div 1 season a wash and to use the game time to develop some upcoming talent instead. There are also talks of scouting the TM, but indecision over what gaps really need filling. With CWC10 looming, some decisions will need to be made and made quickly.

What complicates this situation is that ZCC have been exceptional in the T20 format, and are in 2nd place in Div 1.1 on NRR! Of course, things can change quickly in this volatile format, but one hopes this strong start will ensure another season in the top flight. Raun has found the shorter format more to his speed, averaging 59 at a SR of 124, while Sampath and Ghani have taken 28 wickets between them in 7 games. The same personnel that have struggled in the 50 over have done excellently so far in the T20, so any changes will need to consider the repercussions in the shorter format. Danial Ahsan has been excellent in this format too, with the 2nd most runs and 3rd most wickets - is a call up to the BD Nat squad on his radar?

The Dev side have more or less performed to expectations - bot bashing in Div 3 but bottom half of the table in CWC9. Ewen Rockall and Naeem Ashraf will age out of the side in 6 and 10 weeks respectively, so the hunt is on for their replacement, while tough decisions are being made about their future in the squad. Rumours have it that frontline spinner Tim Chester - with just 10 wickets in 12 competitive games this season - might be cut to make room for the young bowlers.

Financially ZCC have managed to earn close to 600k over the course of the season. This represents around 25% of ZCC's pre-season bank balance. However, with just 2.8 mill in the bank overall, ZCC are not in a position to make any major purchases for world class players.
Yeah, if it's not going well, sell players and build the youths.
I also understand the importance of experience in this game. Tight
 

ataraxia

International Coach
Playing Ashgrove in a SOD rn. It's a side going through a bit of a period of flux between eras. Zahid's aged out of Dev so now needs to keep at senior level as his long-term role will be. But Zac Chambers, the current keeper (and captain!) is better and also makes the team as a specialist bat. So what's happening is Chambers is playing as a specialist bat and has retained the captaincy, with Zahid taking over the keeping duties except for the most important games.

And there are a few players knocking on the door, two of whom are playing in this match: Wilde and Roopak. I've got Roopak–Sellamuttu filling a quota here, so that pushes Naidoo down to #8 where he really should be batting. In general, this SOD lineup is a defensive batter short. But it's always been a bit iffy at #3 and #4. Here Simmonds and Mncwabe have got off to a nice start.
 

ataraxia

International Coach
Comfy win in the end, despite Zosongo's 84 (87). Good match for Naidoo – he's showing real signs of class with bat. As for Hlengwa, on the other hand, he was awful.
 

StephenZA

Cricket Web: All-Time Legend
One of the things I`ve noticed the most about stumped over time is the 'normalisation' of scorecards during a game... particularly with friendly games. But it is what allows for weaker teams to compete with stronger teams but not the strongest teams... who generally have enough strong players throughout the team to overcome.

What do I mean about 'normalisation'... you quite often find that a team doing well early on, will lose lots of wickets in the middle for no apparent reason. And the reverse a team that loses early wickets will suddenly stabilise (almost regardless of batter quality)... or you find that a strong team with a weak lower order suddenly has their poor quality lower order batsmen putting on an extra 50 runs, after the upper/middle order collapsed. It happens when it is 'obvious' that the team should not be bowled out so cheaply. Its also in my opinion why you see so many runouts of middle order batsmen suddenly occurring even to poor quality fielders.

It does not mean there are not blowouts, or dominations but generally most games become 'close' at some stage for various reasons... and the answer is that is how cricket score cards do look... and that's my point, the match engine does not play the game of players at that stage regardless, it seems to want to ensure that the game looks like a 'normal' scorecard. Its why you can almost predict the way a game will go based on the current match situation regardless of batsmen you have left or their quality. Its why there is so many frequently strange single 'events' that occur far more often than happens in real cricket. Its an excuse to normalise the scorecard... for me this is just an observation.
 

cnerd123

likes this
One of the things I`ve noticed the most about stumped over time is the 'normalisation' of scorecards during a game... particularly with friendly games. But it is what allows for weaker teams to compete with stronger teams but not the strongest teams... who generally have enough strong players throughout the team to overcome.

What do I mean about 'normalisation'... you quite often find that a team doing well early on, will lose lots of wickets in the middle for no apparent reason. And the reverse a team that loses early wickets will suddenly stabilise (almost regardless of batter quality)... or you find that a strong team with a weak lower order suddenly has their poor quality lower order batsmen putting on an extra 50 runs, after the upper/middle order collapsed. It happens when it is 'obvious' that the team should not be bowled out so cheaply. Its also in my opinion why you see so many runouts of middle order batsmen suddenly occurring even to poor quality fielders.

It does not mean there are not blowouts, or dominations but generally most games become 'close' at some stage for various reasons... and the answer is that is how cricket score cards do look... and that's my point, the match engine does not play the game of players at that stage regardless, it seems to want to ensure that the game looks like a 'normal' scorecard. Its why you can almost predict the way a game will go based on the current match situation regardless of batsmen you have left or their quality. Its why there is so many frequently strange single 'events' that occur far more often than happens in real cricket. Its an excuse to normalise the scorecard... for me this is just an observation.
@trundler your target convergence theorem applies to Stumped as well
 

ataraxia

International Coach
One of the things I`ve noticed the most about stumped over time is the 'normalisation' of scorecards during a game... particularly with friendly games. But it is what allows for weaker teams to compete with stronger teams but not the strongest teams... who generally have enough strong players throughout the team to overcome.

What do I mean about 'normalisation'... you quite often find that a team doing well early on, will lose lots of wickets in the middle for no apparent reason. And the reverse a team that loses early wickets will suddenly stabilise (almost regardless of batter quality)... or you find that a strong team with a weak lower order suddenly has their poor quality lower order batsmen putting on an extra 50 runs, after the upper/middle order collapsed. It happens when it is 'obvious' that the team should not be bowled out so cheaply. Its also in my opinion why you see so many runouts of middle order batsmen suddenly occurring even to poor quality fielders.

It does not mean there are not blowouts, or dominations but generally most games become 'close' at some stage for various reasons... and the answer is that is how cricket score cards do look... and that's my point, the match engine does not play the game of players at that stage regardless, it seems to want to ensure that the game looks like a 'normal' scorecard. Its why you can almost predict the way a game will go based on the current match situation regardless of batsmen you have left or their quality. Its why there is so many frequently strange single 'events' that occur far more often than happens in real cricket. Its an excuse to normalise the scorecard... for me this is just an observation.
Yeah I don't necessarily agree with this, because actually predicting what will happen in a Stumped game is hardly easy, but there's definitely a kernel of truth. I think it might be more the other way – the Stumped engine has the propensity to get worse teams in strong positions against better teams (which is great). IMO the recoveries you generally see are a symptom of the difference in quality finally shining through. And experience probably is very important to this effect – stronger teams tend to have high-experience players throughout.

My ExP was lower than yours but I guess our friendly just gone fit the pattern. 54 for Levy, 96 for Jupp, but nothing from anyone but the openers. Run out of Davidson was crucial. My bowling attack was a lot weaker – but the ~best I could muster for a seaming pitch – and we were lucky to keep you to 230. Then we were reduced to 146–7, but I thought winning was still eminently achievable with Butler and Naidoo at the crease and they casually compiled the highest partnership of the game to see us home. #batdeep prevailed.
 

SillyCowCorner1

Request Your Custom Title Now!
One of the things I`ve noticed the most about stumped over time is the 'normalisation' of scorecards during a game... particularly with friendly games. But it is what allows for weaker teams to compete with stronger teams but not the strongest teams... who generally have enough strong players throughout the team to overcome.

What do I mean about 'normalisation'... you quite often find that a team doing well early on, will lose lots of wickets in the middle for no apparent reason. And the reverse a team that loses early wickets will suddenly stabilise (almost regardless of batter quality)... or you find that a strong team with a weak lower order suddenly has their poor quality lower order batsmen putting on an extra 50 runs, after the upper/middle order collapsed. It happens when it is 'obvious' that the team should not be bowled out so cheaply. Its also in my opinion why you see so many runouts of middle order batsmen suddenly occurring even to poor quality fielders.

It does not mean there are not blowouts, or dominations but generally most games become 'close' at some stage for various reasons... and the answer is that is how cricket score cards do look... and that's my point, the match engine does not play the game of players at that stage regardless, it seems to want to ensure that the game looks like a 'normal' scorecard. Its why you can almost predict the way a game will go based on the current match situation regardless of batsmen you have left or their quality. Its why there is so many frequently strange single 'events' that occur far more often than happens in real cricket. Its an excuse to normalise the scorecard... for me this is just an observation.
1693484398620.png
 

Attachments

StephenZA

Cricket Web: All-Time Legend
Yeah I don't necessarily agree with this, because actually predicting what will happen in a Stumped game is hardly easy, but there's definitely a kernel of truth. I think it might be more the other way – the Stumped engine has the propensity to get worse teams in strong positions against better teams (which is great). IMO the recoveries you generally see are a symptom of the difference in quality finally shining through. And experience probably is very important to this effect – stronger teams tend to have high-experience players throughout.

My ExP was lower than yours but I guess our friendly just gone fit the pattern. 54 for Levy, 96 for Jupp, but nothing from anyone but the openers. Run out of Davidson was crucial. My bowling attack was a lot weaker – but the ~best I could muster for a seaming pitch – and we were lucky to keep you to 230. Then we were reduced to 146–7, but I thought winning was still eminently achievable with Butler and Naidoo at the crease and they casually compiled the highest partnership of the game to see us home. #batdeep prevailed.
230 was never defendable... and my lower order batsmen are in terrible touch, so it did not surprise me to lose that match. I`m just commenting on general trends I have consistently seen throughout my now few years (??) of playing stumped.

For me it is consistent... unless you have huge disparity in expert preview rankings, the games are quite predictable. The number of times I will have a good opening partnership and than fall short of 300 is common, regardless of the batting order or who was placed where. If I have a poorer opening partnership my middle order tends to recover. But then often you find that just as you get back into the game you suddenly lose wickets and innings collapses. Then you will watch the second innings and it will follow one of those two sort of trends.

I mean how often do you get 'lucky' and take out the oppositions top batsmen with some good bowling but then their number 6 who is 20 years old with 35 skill suddenly scores 80 odd, against the apparently much higher quality bowlers.

And so I have an opinion that the match engine is setup to ensure that the game looks like a 'normal' cricket game overall. Its not about the circumstance right then in the match. Its not about that bowler vs that batsmen right then... it feels like there is a background weighting to ensure that it 'feels' like its a proper cricket match. If there is a huge consistent disparagement between batsmen and bowlers that eventually overcomes the weighting. (like 65K+ bowlers bowling to 45K+ batsmen). But the engine does allow for the game to consistently lose your 43 skill bats to the 27 skill bowler, if the match engine determines so... and the 25 skill lower order bat that never scores runs will hammer the 42 skill bowler because the engine indicates that you should score more than 200 on this pitch...

And I know that the argument of well... strange stuff happens in cricket (in real life)... but it is strange because it is infrequent. It should not be consistent in its frequency.

Everything averages out over the long term, because at times you will benefit and at times you won't... I'm still not a fan of it overall. I do think its more pronounced in friendlies than in the match day games. And least effects the SOD matches.
 

cnerd123

likes this
I've actually had the privilege of 'looking under the hood' in terms of the code (Rob once shared it with me) and I can honestly say that, from what I've seen, the game legit calculates every ball as an individual event.

The 'convergence theorem' I referred to earlier is a phenomenon trundler, and several other posters here, have noticed in RL cricket - particularly ODIs. Team scores generally tend to converge to a 'normal' looking score, whether that is slowing down/losing clumps of wicket after a good start, or recovering from a poor one. Start watching ODIs with this perspective and you'll see it happen all the time too.

We overplay the gap in skills sometime. A 43 bowler doesn't always bowl like a 43 bowler. In some conditions and situations they'll deliver performances like a 55 bowler, in other cases like a 31 bowler. Najmul Hossain Shanto - with a career average of 24 - just hit an excellent 89 vs a top quality SL team today, while Shakib scored 5 and Mushy scored 13. That doesn't mean the IRL ODI match engine is broken. Cricket just works this way sometimes. Every single ODI ever played will have something odd in it. Nature of the sport.
 

Top