afridi118
International Coach
- Joined
- Oct 11, 2004
i know but we never no what can developer do loal
ICC future features
- Thread starter Sureshot
- Start date
i know but we never no what can developer do loal
Dragon Fire
Club Cricketer
- Joined
- May 4, 2010
- Online Cricket Games Owned
What about occasional rain in OD games? Ive been playing five or six years and never had rain. Duckworth Lewis here we come.
It'd be a misconception to think that adding Indian domestic season would rope in lots of NEW Indian fans for this game. The vast majority of people in India & probably sub-continent in general, are least bit interested in the domestic cricket, even though Cricket has such a great following there but that's just limited to international "stars", most people wouldn't even be able to name 10 non-international domestic cricketers from their local side. Why do you think a Cricket-crazy country like India which is a monetary powerhouse of the cricketing world can't produce eleven (or more) world-beaters to form a world-beating team while countries with populations of less than 5% of theirs have managed to do it ? (I know India are ranked first on ICC table but they hardly have the aura possessed by the Aussie team for about a decade, India's batting is pretty good but bowling is nowhere compared to the Aussie equivalent or WI for that matter when they were world-beaters). When we look at English & Aussie domestic scene, at least a few hundred people are present in the stadiums to watch even a group match while in India, the domestic cup finals pass by with empty stands.
The reason I mention this is because adding Indian domestic season would probably be a MASSIVE undertaking but the returns may not be what the developers might be expecting in terms of sales figures, revenues, etc so developers should tread with caution while directing their limited resources to create new leagues & look into their commercial viability. I've just used India as an example for making a wider point about adding new domestic leagues or associate nation teams, etc.
Agreed, I think the game-play must be given priority over adding new leagues, be it IPL or domestic leagues of countries. I'm sure there's a lot that can be improved about the current game-play & I've seen very many great suggestions from users on many threads. I also really hate T20s & IPL so don't give a f about it, they should only be looked into once ICC has nearly perfected the game-play aspect (although I don't think it'll ever be absolutely perfect but it can get as close to it as possible I suppose). Aussie domestic league was a nice addition though since it's the game's second biggest market after England but I'd be reluctant to support the addition of other leagues before game-play has been vastly improved.
Chewie
BCCI President
With regards to domestic competitions, to increase the number of sales by the largest number, either the NZ domestic structure or the IPL should be included. The other countries either don't have enough people who play the game, or don't follow the domestic cricket in their countries.
I've said this before, but NZ and SA I'd assume would be the easiest, as they both have six DOM teams, so surely you could just follow the exact same model as how the Aus doemstic cricket works.
Also all the players are already in the game, so from someone who knows nothing about this (me), I'd say you would just have to copy the Aus one and edit the teams/player/code, or whatever.
Also all the players are already in the game, so from someone who knows nothing about this (me), I'd say you would just have to copy the Aus one and edit the teams/player/code, or whatever.
Yeah, TBH I don't really care about SA DOM.
My main point that I made when it first came out was, NZ DOM is pretty much the same as AUS DOM, so it wouldn't be too hard to create NZ DOM, since AUS DOM and ALL the NZ players are already created.
My main point that I made when it first came out was, NZ DOM is pretty much the same as AUS DOM, so it wouldn't be too hard to create NZ DOM, since AUS DOM and ALL the NZ players are already created.
I find bowling to be much more satisfying than batting. Whereas I have a sense of being able to bowl to fields, set fields etcetera I find batting doesn't involve me in the same way. Of course I need to be able to read the match situation and read my players qualities correctly and to use the aggression settings accordingly but I wonder if it is possible to revamp the whole batting side of things so that you feel more involved as a player.
It would be helpful as well for there somehow to be some information or help as to why something isn't working. I mean in a normal cricket game you have a timing meter or whatever that tells you how you are batting.
I know this game and idea is based on a whole different concept but I find myself frustrated often as to why a batsmen isn't scoring quickly or gets out etcetera. It all feels to random and too much out of my control.
I also think there needs to be much more information and coaching for the beginning player and maybe less knowledgeable player to be able to really get the most out of this game.
Sorry if it sounds like a mini review but just a couple of thoughts!
Agreed. I definitely feel more involved in the game while bowling/fielding but nowhere as much while batting; I don't know how this can be improved upon without turning ICC into "Brian Lara" (which I'd hate to see) but we've plenty of fertile brains & they'll manage to come up with something
enigma added 2 Minutes and 0 Seconds later...
My future features list is probably too long to remember everything
but I'll just post a couple from the top of my head1) I'd really like bowlers' preferences being visible like if a bowler has out/in-swing as his stock delivery or that he can only swing one way & we can train him to develop the other swing & an out-swing bowler getting more wickets behind the stumps through edges while an in-swing bowler getting more bowled & LBWs; is a bowler very aggressive & gets wickets but can be expensive or a defensive one like Elham or both like McGrath & many more such preferences can be implemented.
2) I'd really like more stats on wicketkeeping & fielding abilities. Right now, we just choose keepers for their batting so to bring keeping into forefront, there should percentages of successful catches/stumpings out of all the catches/stumpings presented, percentage of byes given per overs kept. For fielders, their slip-catching percentage; inner-ring fielders' catching percentage & ground-fielding ability; boundary-riders' catching percentage, ground-fielding & how good their throw is from the boundary AND OF COURSE, all of these things actually affecting the gameplay like bad keepers/fielders dropping more catches & giving byes & mis-fielding, etc without which it'd be just be a "cosmetic effect" I suppose.
3) Taking a cue from what I've read from other users abou this, I'd like more control over the county finances like being able to add more seats or tweak the ticket prices up/down slightly to maximize revenues or being able to build floodlights & lending the ground for matches & earning more revenues from that since floodlit games will bring in more revenues, managing sponsors & anything else that can possibly help in generating revenues.
4) Copy-paste of my post from Childish Things forum -:
"One of my bowlers has been going for less than 6 RPO in the last few consecutive T20s but his form/confidence is being shown as ZERO, serious flaw this.
ICC should definitely have a look at this issue & have an in-game system of flexible RPO "benchmarks" for RPOs for different formats of the game & bowling at an RPO less than the respective benchmark should result in an increase in form/confidence (coupled with wickets taken, importance of those wickets & total overs bowled) & an RPO higher than the respective benchmark should result in a decrease in form/confidence. Benchmarks can be like for example, for long-form games, an RPO of 3.5 or opposition team's run-rate whichever is HIGHER; an RPO of 5/4.5 for 40/50 overs games (respectively) & opposition team's run-rate whichever is LOWER; for T20s an RPO of 7.5 or opposition team's run-rate whichever is LOWER, etc.
One must realize that bowlers' form/confidence is not just limited to wickets taken but often, good economical spells with a few "near misses" with no wickets or less wickets can make a bowler feel just as good as taking a bucketful of wickets and then they carry forward this good feeling (form/confidence) stemmed from economical spells into next few games & actually end up taking a bucketful of wickets."
Last edited:
Well, only the developers would know what the actual situation is regarding country-specific sales so I'd rather not comment on that but I'd just want them to look at its viability before creating any league since adding new domestic league, IPL or associate countries caters to only a certain section of its customers but good game-play improvements will be appreciated by everyone & it'll also pull in some new customers as well.
About adding new leagues, lets say they add IPL (or another league) next year & satisfy the "IPL crowd" & gain some new customers but due to IPL eating into their time & budget didn't get to spend a lot of money or efforts on improving the game-play a lot, will its older customers who aren't interested in those new additions buy ICC? I wouldn't & I'm sure lot of other non-IPL-crowd might not. Will those who bought this year due to the addition of Aussie-domestic buy next year if the game-play didn't change a lot but IPL or other domestic leagues were added? May be but likely not. Will the IPL-crowd buy the game the year after it has been added, if there are no big game-play improvements but only another domestic league is added? May be but likely not.
The bottomline is it's a small game with a small team & small budget which is struggling to keep its head above the water & they ought to be very selective in how they choose to spend their limited resources & they can't afford to lose their current customers & almost every one of them will buy again if there are a lot of good game-play improvements but additions of new leagues will only get a certain section to keep buying it.
Don't get me wrong, I know what you guys are trying to say when you compare Aussie & NZ leagues, etc but personally, I'm not a coder so I don't know how easy or hard it would be neither do I know about how much it will boost the game's sales & how commercially viable each league might be so I'd just like to leave that judgement to the developers as they're the ones in the best position to make that judgement. Cheers.
Not sure if this has already been said but one thing I would like is more tests per test series, because in 2010, nearly every series I have played as New Zealand only has 2 tests and this is kinda annoying.
I would also like to see RPO affect form changes, for example if someone hits 40 off 30ish balls, they get less form than a 50 of 80 balls. Same for bowlers, but only in limited over games.
I would also like to see RPO affect form changes, for example if someone hits 40 off 30ish balls, they get less form than a 50 of 80 balls. Same for bowlers, but only in limited over games.
Highlights/graphics: bring back slow-mo and freeze-frame. I have a beautiful gallery of brilliant catches from ICC06. Why oh why can't I do the same with the 3D engine? Failing that, something to make the ball easier to follow. Honestly sometimes, even after viewing the highlight multiple times, I have to look at the wagon wheel to work out where the four or six actually went.
Unsuccessful stumping appeals and missed stumpings: the batsman doesn't have to wander halfway down and then just stand there like a lemon, to get out stumped. He just needs to plant his front foot down the track, and then there's the issues of did he drag his back foot, did the keeper take it cleanly, and (optionally because it's graphically trickier) could he get back in time. The first two could be implemented with only the slightest tweak to the highlights.
Throws to the bowler's end (naturally including run-outs/appeals)
Run-outs other than on direct hits.
When a batsman retires, the edit field screen will not show the new batsman's wagon wheel. This continues to the end of the innings - the wagon wheel of the last man in is not selectable.
Shots off no-balls never show up on the batsman's wagon wheel.
Make the saves from one version importable and playable on the next. To be honest I've never got a save to 2034, but I can certainly imagine how heartbreaking it would be to have to bin hundreds of playing hours and start again - every year. More importantly where moolah is concerned, what a disincentive this must be to buy the next version!
Team stats for one-dayers and T20, not just first class. The star one-day or 20/20 bowler - who might rarely or never even bowl in first-class - deserves recognition too!
A highlights package - all boundaries and wickets say - viewable (at the very least) immediately after the game.
Credit given somewhere (preferably accessible later on) as to who pulled off the run-out. Similarly 'name & shame' the bloke who dropped the catch. I can work these out for my own players, but it's simply impossible for the opposition unless you recognize their hairstyle or whatever on the highlights. Yet these are details that you are going to want to include if you write a story. So presumably those who give these details in stories have to make them up.
A separate 'batsman aggression' bar for singles (no not that kind of singles bar :laugh). You have to be able to tell your no. 9 when he comes in in the 2nd last over: "No don't slog! No don't stonewall! But DO get off strike at the EARLIEST opportunity (if not sooner)!"
Powerplays should not be allowed to start mid-over.
Correct field restrictions need to be enforced. Whether there have to be five in the circle, or seven, or whatever.
Field restrictions are enforced by the umpire calling a no-ball, not by preventing you from setting the field. Naturally to make this work, the game must stop (regardless of highlights level) immediately to let you remedy the situation. Also, the edit field screen must list how many fieldsmen are outside the circle, because sometimes it's hard to tell if it's borderline.
Rain in one-dayers: if you can't do Duckworth-Lewis for whatever reason, I don't mind if you fudge something, but rain interruptions are part of the game.
Retain stats for retired players: surely you don't delete Tendulkar from the database when he retires!?
Players retired hurt who return to play a further part in the match. Sometimes IRL quite seriously injured players come out to bat next innings (and occasionally the same innings).
Batsmen out bowled other than clean-bowled: often IRL the ball hits the bat and/or the pad first.
Bat-pad catches: many if not most short-leg/silly point catches should come off both bat and pad.
Increased aggression on free-hits: if it's already implemented automatically then well done and that relegates this from a must-have to the wishlist, but I would really like the game to stop, and to be given the option of deciding exactly how aggressive I want to be. Some players' eyes light up so bright...they can't see a thing
I'll stop now. They're the really important ones...
Unsuccessful stumping appeals and missed stumpings: the batsman doesn't have to wander halfway down and then just stand there like a lemon, to get out stumped. He just needs to plant his front foot down the track, and then there's the issues of did he drag his back foot, did the keeper take it cleanly, and (optionally because it's graphically trickier) could he get back in time. The first two could be implemented with only the slightest tweak to the highlights.
Throws to the bowler's end (naturally including run-outs/appeals)
Run-outs other than on direct hits.
When a batsman retires, the edit field screen will not show the new batsman's wagon wheel. This continues to the end of the innings - the wagon wheel of the last man in is not selectable.
Shots off no-balls never show up on the batsman's wagon wheel.
Make the saves from one version importable and playable on the next. To be honest I've never got a save to 2034, but I can certainly imagine how heartbreaking it would be to have to bin hundreds of playing hours and start again - every year. More importantly where moolah is concerned, what a disincentive this must be to buy the next version!
Team stats for one-dayers and T20, not just first class. The star one-day or 20/20 bowler - who might rarely or never even bowl in first-class - deserves recognition too!
A highlights package - all boundaries and wickets say - viewable (at the very least) immediately after the game.
Credit given somewhere (preferably accessible later on) as to who pulled off the run-out. Similarly 'name & shame' the bloke who dropped the catch. I can work these out for my own players, but it's simply impossible for the opposition unless you recognize their hairstyle or whatever on the highlights. Yet these are details that you are going to want to include if you write a story. So presumably those who give these details in stories have to make them up.
A separate 'batsman aggression' bar for singles (no not that kind of singles bar :laugh). You have to be able to tell your no. 9 when he comes in in the 2nd last over: "No don't slog! No don't stonewall! But DO get off strike at the EARLIEST opportunity (if not sooner)!"
Powerplays should not be allowed to start mid-over.
Correct field restrictions need to be enforced. Whether there have to be five in the circle, or seven, or whatever.
Field restrictions are enforced by the umpire calling a no-ball, not by preventing you from setting the field. Naturally to make this work, the game must stop (regardless of highlights level) immediately to let you remedy the situation. Also, the edit field screen must list how many fieldsmen are outside the circle, because sometimes it's hard to tell if it's borderline.
Rain in one-dayers: if you can't do Duckworth-Lewis for whatever reason, I don't mind if you fudge something, but rain interruptions are part of the game.
Retain stats for retired players: surely you don't delete Tendulkar from the database when he retires!?
Players retired hurt who return to play a further part in the match. Sometimes IRL quite seriously injured players come out to bat next innings (and occasionally the same innings).
Batsmen out bowled other than clean-bowled: often IRL the ball hits the bat and/or the pad first.
Bat-pad catches: many if not most short-leg/silly point catches should come off both bat and pad.
Increased aggression on free-hits: if it's already implemented automatically then well done and that relegates this from a must-have to the wishlist, but I would really like the game to stop, and to be given the option of deciding exactly how aggressive I want to be. Some players' eyes light up so bright...they can't see a thing
I'll stop now. They're the really important ones...
jacobfelix
International Coach
Just like for all players they have the Batting preferences like " Strong on the offside" ; " Spin Specialist" etc....for a bowler they should give.....probably say, What are his strengths? ...for ex, Inswinger expert ; Yorker expert ; Doosra expert
Last edited:
