SillyCowCorner1
Moooo
I'm happy that TNT didn't chase down a paltry 97 in say..15 overs. GG made them work a bit. They made 99 in 24.3 overs...so that's probably the shining light I take out of this match.
-
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!
- Thread starter GHick405
- Start date
SillyCowCorner1
Moooo
Edge of the seat stuff here between Mooo and the PP's
Odds are in their favor to knock off the remaining 27 in 27 balls
Odds are in their favor to knock off the remaining 27 in 27 balls
andruid
Cricketer Of The Year
I had a really low start-up point. My roster is still in the purge phase
If this is only regarding Dev , don't read to much into it . If it is Senior teams its a bit deferent . Provide some games your upset about maybe we as a collective can give some input . Some quality managers on this forum . If it was rhetorical and only due to current results . Its stumped it happens RNG is insane .
cnerd123
likes this
To FHK's credit:
1) dry deck suited our 20 overs of spin
2) Chow Hang-tung and Sze-yiu Koo are our two best players and both put in excellent all round performances
Dev cricket is a complete crapshoot anyways haha. Most upset prone format as Krypto says. Low experience, fielding and stamina all cause good players to fail fairly often
SillyCowCorner1
Moooo
Table-toppers, The Net Theorists have a NRR of +2.16
Bottom dwellers, Chips Mwitu with a NRR of -2.16
Coincidence much?
Bottom dwellers, Chips Mwitu with a NRR of -2.16
Coincidence much?
Jarquis
Cricket Web: All-Time Legend
Also bowled 20 overs of spin… the ratings game was ridiculous (proportionally) and it didn’t even end up being close
SillyCowCorner1
Moooo
A couple of changes have been made during the past couple of hours following the CWC9 Round 3 matches,
i) Moooo mowed down the size of their squad to 21, some big names got fired.
ii) GG CC ordered their groundsmen to to prepare pitches that are faster and bouncier...but more moisture, suiting the style of majority of the players in the squad. One of our bowling coaches, Babar Ijaz used to be the fastest bowler in GG team's history, so the culture should stick around and continue.
i) Moooo mowed down the size of their squad to 21, some big names got fired.
ii) GG CC ordered their groundsmen to to prepare pitches that are faster and bouncier...but more moisture, suiting the style of majority of the players in the squad. One of our bowling coaches, Babar Ijaz used to be the fastest bowler in GG team's history, so the culture should stick around and continue.
SillyCowCorner1
Moooo
Making a statement. He fooled the scouts.
cnerd123
likes this
Tough decisions to make on the TM today
We have a 41 pot bat in our Dev team who is a bit of a filler, and a spot has opened up in our training program to get a new kid into the system.
There are three bats on the TM.
Do I go for:
25/44 Precocious 15.13 with 12 fielding for around 100k
33/45 attack skewed 18.12 with 11 fielding for around 500k
Or upgrade my 41 pot filler to another 41 pot filler, but with 19 fielding + bullet arm, and hold off for a better prospect.
Hmm.
We have a 41 pot bat in our Dev team who is a bit of a filler, and a spot has opened up in our training program to get a new kid into the system.
There are three bats on the TM.
Do I go for:
25/44 Precocious 15.13 with 12 fielding for around 100k
33/45 attack skewed 18.12 with 11 fielding for around 500k
Or upgrade my 41 pot filler to another 41 pot filler, but with 19 fielding + bullet arm, and hold off for a better prospect.
Hmm.
cnerd123
likes this
Would slot right in as a Ed Halliday / Shabadpreet Samra replacement for us too.
I've got the 15 YO for around 100k. Not a world beater but will do a job for us. I do want a long-term prospect for the senior side tho, so still debating on if I should drop half a mill on Junaker. But no relevant talents, meh fielder.
StephenZA
Cricket Web: All-Time Legend
This is what I hate about the stumped engine...
If this was Nick Smith taking my bowlers apart to win the game, I would not mind losing.
But to basically have two youngsters with no real observable skills that have likely been put on a 8/9 attacking skill and because the engine promotes attacking as better than playing circumstances the partnership of these two youngsters have likely lost the game for me... if I lose to a high skilled batsmen I don't care. The consistency of the engine promoting this sort of play bothers me.
But the consistency of winning/losing games to unexpected and statistically unlikely partnerships and low skill players is truly demoralizing in games where monies is everything and relegation can kill a team. And before anybody says that this happens in cricket... the whole point is it should be the exception not the norm, maybe once a season this should happen, not every second or third game.
And you can overcome it... by having a team that has far greater skill than the opponent, and this normalizes near the top where everybody has good teams. But if you are building the team and need monies because its truly the only way to become a competitive team in the long run, it hurts.
If this was Nick Smith taking my bowlers apart to win the game, I would not mind losing.
But to basically have two youngsters with no real observable skills that have likely been put on a 8/9 attacking skill and because the engine promotes attacking as better than playing circumstances the partnership of these two youngsters have likely lost the game for me... if I lose to a high skilled batsmen I don't care. The consistency of the engine promoting this sort of play bothers me.
But the consistency of winning/losing games to unexpected and statistically unlikely partnerships and low skill players is truly demoralizing in games where monies is everything and relegation can kill a team. And before anybody says that this happens in cricket... the whole point is it should be the exception not the norm, maybe once a season this should happen, not every second or third game.
And you can overcome it... by having a team that has far greater skill than the opponent, and this normalizes near the top where everybody has good teams. But if you are building the team and need monies because its truly the only way to become a competitive team in the long run, it hurts.
Last edited:
cnerd123
likes this
two dropped catches tho, and some poor balls that got hit for runs mixed in with the good balls. Pullen in particular seems a decent batter with some good form coming into this game. Dar might be a hack who got lucky. gung ho nature suggest his skills lean to attack, and he's batting fairly high up, but has no real runs behind him. Could just be his breakthrough innings.
Overall given the conditions TNT probably got a par score. Low exp bowlers at the death on a flat deck are always prone to being taken apart a bit. The opposition did bowl better and have a higher expert preview, so you expect them to win, and as it turns out they did. Maybe just not in the way you expect. Dar's innings of a lifetime was the difference.
Overall given the conditions TNT probably got a par score. Low exp bowlers at the death on a flat deck are always prone to being taken apart a bit. The opposition did bowl better and have a higher expert preview, so you expect them to win, and as it turns out they did. Maybe just not in the way you expect. Dar's innings of a lifetime was the difference.
StephenZA
Cricket Web: All-Time Legend
My complaint was not that I lost the match... its how the match was lost.
The problem with that sort of erratic match engine behaviour is how do you plan a game? How do you plan a strategy? How do you determine whether a player is worth something or not... I honestly don't mind losing against a better team, or a skilled player having a great day, or a team that got a bit lucky on occasion in a tight contest, or where my players just failed on a day... what I get unhappy about is when I am in a winning position and suddenly lose because it feels like the randomness of the engine was set high... and this is a frequent occurrence. And don't get me wrong, I have benefitted from this as well by winnings games I should not. But I still don't like it I`m not a man who enjoys playing dice games. Particularly when the effect of relegation can cost a team a lot.
And this is particularly bad for new teams, because going up against teams/managers that have resources in the bank but more importantly know how to play to the match engine...(not to necessarily set realistic cricket orders!). This creates a win more situation. And it turns it from a cricket simulator into a pure financial manager engine gaming system... It is less pronounced at the high end because those managers are generally playing on an equal footing both management experience wise and also player skill wise.
Ultimately I`m not gonna stop playing stumped, I hope to develop a great team that can overcome these issues and system problems... but I`m certainly not gonna pretend to be happy that the randomness of the game is a bit to high and occurs to often for me to totally enjoy.
As an aside you mention the experience stat, I have a problem with how experience is used in stumped, as it is probably the single most important stat. I learnt that using Ncanana, who skills wise was well below many of my other players but because of experience used to consistently give good performances. Whereas my other better quality players, higher waged players could not be trusted because of lack of experience... you also get hurt developing players with lower experience in a decent team because it increases run out opportunities etc etc...