It could only be a dream

Ste said:

Has anyone still got the spreadsheet?

Click to expand...

List of Game play Issues to be fixed in priority order




1) Human controlled teams reverting to default XI line up after game is saved and reloaded
This applies to one-day matches as well as first class/test matches. Whether playing a friendly, international or tour etc, an issue arises as soon as you pick a team that has players that do not belong to the programs default team line up.
If a match is played all the way through with no saving and reloading of game then there is no issue. However if the game is saved, the following issue arises upon reloading:
a) In one-day matches, as soon as the 2nd innings commences your (human) team resorts back to the program default XI line up. So any players you bring in from the squad outside the default XI are replaced with the default players once more.
b) In test matches, as soon as the first 2nd innings commences the same issue as mentioned in a) above occurs. Any players you used from outside the default XI are again replaced with the default XI players you removed in the first place

1b) Cannot chose default field settings with non default XI players
Following on from 1) above, as soon as a game is saved and reloaded the following happens with non default XI players you have chosen from your squad to play in the match
a) Whenever you select a non-default XI player to bowl, you can only use the normal 1 default field. The program allows you to choose any field you desire from the usual list, but only the normal 1 field is used when actually playing the game. This is most bizarre when in the restricted overs of an ODI, as more than 2 fielders are in the outfield. Also, it removes any tactical element from the game as you are stuck with that field for the remainder of the match

Point 1 means that the whole point of picking a squad for a tour, test series etc is defeated, as the game will only allow you to play with the default XI it chooses, and not what you choose.


2) CPU running between the wickets (all skill levels)
The CPU?s batting judgment of when to take a run (especially when ball is hit in the direction of mid on/off is poor, even on the HARD level. Too many suicidal runs taken (even in tests) which result in easy run outs. The readme that comes with the game says that patience is the key when it comes to taking wickets in tests. At present no patience is required as every few overs an easy run out opportunity arises, resulting in even the best teams posting low scores with 5+ run outs evident on many occasions in an innings. (very unrealistic).


3) Statistics
-An innings, which ends while using ?auto play? or played fully by a human, will have an incorrect scorecard when all 10 batsmen are out. All 11 batsmen will be recorded as out, with often one batsmen listed as bowled or LBW without a bowler?s name shown
-Records from tour matches (i.e. touring international side vs. local side) are incorrectly listed under Test (they are actually first class games). They also seem to record the opposition wrong ? e.g. a record I got for Australia vs. West Indies A was recorded as Australia vs. Australia



4) Wicket Keeping
Far too many byes in Test matches. Inability of keeper to take simple catches or stop the ball from going for sn unrealistic number of extras.


5) Auto play issues
Many reported instances of auto play crashing the game back to desktop ? no matter which option is used (end of innings, to next wicket etc). Also if for example, you auto play a 50 over ODI, often a bowler will have bowled more than his 10 allotted overs in an innings.


6) Fielder on the pitch (tests only)
After taking a wicket in a test match, for the next ball only, as the bowler runs up to the wicket, a fielder stands on the pitch half way down the wicket. He can field/catch the ball as normal


7) Stamina bar does not reduce (tests and ODI?s)
No matter how many overs a bowler bowls, his stamina bar never reduces. There have been recorded instances of bowlers bowling 17 overs in a row in tests and their stamina bar is still at maximum. The whole idea of implementing a stamina bar to increase the strategy element in picking different types of bowlers depending on pitch conditions etc is defeated. You can pick two fast bowlers for a green pitch
in tests, and bowl them both all day long (i.e. 45 overs each) without any downturn in their performance

Click to expand...

Will p said:

hahahaha Zim have you ever heard of a Shrink, check it out, you must be mad if you;re dreaming EA had made cricket 2004 good!

Click to expand...

zimrahil said:

The appointment has already been made...............

Click to expand...

Shailesh said:

or you know what to do next time you see jw

Click to expand...