Dear big ant studios,
Since we are a cricket loving community and you are the only company that makes a cricket game. Every game since DBC14 had its own flaws and you seems to be taking cricket game backwards than evolving. Majority of the community has no hopes with cricket 24, hence requesting you to look at the below points for cricket 26 or any iterations of cricket you plan to make after this fiasco.
1. Scrap the current engine you are working on as that will never give a complete engine.
2. Start from the very basics and create two types of batting animations for each batting style. One where a batsman is skilled and one where a batsman is a tailender.
3. Movement of the batsman should be solely based on the user input at least in higher difficulties. Currently the defensive shots would make the batsman reach to the pitch of the ball which negates the chance of edging while playing defensive shots. Reverse sweeps and sweeps to be connected against fast bowlers should have lesser chances. Currently players can play the entire innings with sweeps against any type of bowler which is impossible IRL.
4. Running speed of the batsman should be solely basis of batsman speed and not their height. Is a 5"4 batsman has a speed of 80 and a 5"8 batsman has a speed of 60 then the former should be a able to complete a run faster than the later. The AI running of the striker and non striker should be based on their judgement numbers. If the striker a has good judgement and the non striker has a poor judgement number then there should be a higher chance of a run out.
5. Work backwards with 6 hitting capabilities. Like the batsman with highest power and timing should be able to hit 110-120 meter sixes. So if the power and timing it less the six distances should be way lesser. Right now any tom, dick and harry can hit 120 meter sixes.
6. Bowler is pretty much sorted in the engines, the only addition being bowler running to collect ball / kicking the ball and looking for a run out opportunity than giving an easy single to the batsman. The bowler chances of taking a return catch or fielding at their own bowling should be based on their judgement and running speed. The AI should be tuned in way that regardless of the batsman being rhb or lhb the line of the bowler should be 5th stump line majorly and never at the leg side unless a batsman's leg glance skills are too weak.
7. Wicket keeper: first of all there should be an option to bring him up for medium pacers right to the stumps. Wicket keeper should only be diving in the absence of a first slip and should always be near the stumps if the return throw is coming near the stumps. Right now keeper stands 2 feet away and by the time a run out attempt is completed, batsman will be yawning their way into a run.
8. Close in fielders : only in case where there is an edge or mistimed shot or a loopy ball they should be able to catch / field a ball. In no sensible world a close in fielder should be able to dive and pluck a catch which is perfectly timed.
9 circle fielders : loopy throws to the keeper and bowler has to go away. It is allowing batsman to complete a run with ease even though it should be a tight one.
10. Out fielders : after a stop there shouldn't be a delay to return the ball. Catching mechanism needs to be updated.
11. Pitches : pitches should behave as close to real life pitch behaviours in terms of swing/bounce/seam/spin etc. Users shouldn't be pushed to create 100s of difficulties to enjoy a game which is been sold at 4299 INR. We are spending far too much time tweaking physics for a game just to enjoy it where we have paid a premium amount.
12 batsmen mentality and pacing the innings. Create a Matrix for different types of batsman based on their mentality. The Matrix should mentality vs situation and based on the outcome the batsman should pace the innings. For example look at the below screenshot. Similarly create situations and based on the situation do a logical coding which will make batsman behave per situation than playing like a mindless robot. Things like safe guarding a lower order batter and chasing an innings should be all coded in similar manner.
12. Career mode should have more depth : like in fifa our performance and training should tell us whether we are close to make it to the XI or we get benched. Player achievements should be called out by the commentators.
When you are selling a game at premium we expect the game to be a premium one and not somewhere were we have to compromise and do a lot of work ourselves. Been very critical of you for couple of years but to be honest it's only because how you treated us in the last year's. Number 1 rule is "customer is king". If you can't take constructive criticism from you premium paying customers then you should be releasing games at a lesser price. Then we will be happy to think you are doing as a service and we have to be happy with what we got.
Regards,
Once a true big ant fan, now one of your biggest critique.