Cricket 2004 bugs list

I can't remember anyone else posting these bugs, so forgive me if they've been mentioned before.

1. Playing a 4/5-Day match. How do you know what day you are playing? That might sound stupid, but I went back to play a Pura Cup match today and can't find where it tells me what day it is.

2. Anyone notice how the commentating gets confused and calls Deep Mid Off Deep Fine Leg, or vice-versa?

3. How about when you are starting a new day and find the batsmans confidence meter is exactly the same as when he finished the night before. Now THAT is realistic...NOT!!!
 
Regarding the stamina bug,i can see it works internally and also updates the values,its just a display bug,the stamina is taken from the 81(d) byte from the bowler/player name.A long value is taken.

Code:
here is the code which takes and display

          MOV EDI,DWORD PTR DS:[EDI+68]  ;Takes the long value from the offset of the player and stores it in EDI
          SHR EDI,12 ;Right shift EDI 12h times
          AND EDI,1F ; AND EDI with IFh;Here the result is always 14h for some reason :confused: 
          LEA ECX,DWORD PTR DS:[EDI+EDI*4] ; so 14h + 14h * 4 = 64h = 100d hmmm~,here is the bug

Thats why the meter stays at 100%
 
Last edited:
Originally posted by sam2002
Regarding the stamina bug,i can see it works internally and also updates the values,its just a display bug,the stamina is taken from the 81(d) byte from the bowler/player name.A long value is taken.

Code:
here is the code which takes and display

          MOV EDI,DWORD PTR DS:[EDI+68]  ;Takes the long value from the offset of the player and stores it in EDI
          SHR EDI,12 ;Right shift EDI 12h times
          AND EDI,1F ; AND EDI with IFh;Here the result is always 14h for some reason :confused: 
          LEA ECX,DWORD PTR DS:[EDI+EDI*4] ; so 14h + 14h * 4 = 64h = 100d hmmm~,here is the bug

Thats why the meter stays at 100%

In English please???:)

Anyway ofcourse Sam can fix it:D
 
LOL another commentary bug is when the ball is tucked around the corner to Backward Square and Richie says "The ball has pierced the OFFSIDE field".
 
LOL....so common I did not even want to mention it....the value of this game degrades with each post so by now I think the MRSP should be 10p

:)

Anyone care to argue?
 
Oh..Oh..Oh..I have another one. When a fielder picks the ball up close to the boundary and throws it back to the keeper, Richie calls it a 4. Meanwhile, the ball goes sailing over the keepers head for 4 overthrows. So Richie tells us how it was a wonderful cover drive for 4. More to come...then when you check your scoreboard you find that there was only the runs made by the batter while the ball was going to the boundary in the first place.

Everyone follow that? LOLOL
 
Okay, some more bugs that drive me mad...

------------------------------------------------------------------------------------
I have'nt tested this out in test matches yet, but I am sure it will be the same as one day games:
------------------------------------------------------------------------------------

*When putting a fielder in a further back slip position, as if they took some steps backward, when a ball is edged to them, they dive foward to catch the ball. The problem is, it repeats the dive about 3 or 4 times before the umpire signals 4 runs. So what I am saying is...The fielder dives and catches the ball...then he appears in his original position (with the ball) then dives again with the ball in his hands, then repeats.

------------------------------------------------------------------------------------
Then I have a runout issue. I don't know if this is because of the AI patch I have installed or if this has not been affected by the patch and was always this way. (I am playing the game on the hard setting)
------------------------------------------------------------------------------------

*I have had this at least in 3 matches playing the World Series. After between 80/5 or around 90/5 (for all 3 teams I played against) the computer batsman would hit the ball, mainly on side or off side drives. The ball would go directly to one of my fielders and as he picked up the ball, the computer batsman would run. Suicidal runouts, 5 off 5 balls bowled. That is really stupid...so you could just as well say when they are 5 or 6 wickets down, the game is over because they will run themselves out.

*Currently, I am having a way too easy time with these AI bastman. I bowl them all out under a hundred runs because they edge almost every ball behind to my keeper or slips. At first I complained that I was getting no edges...now...it's ridiculous. AI patch problem? or am I just bowling so well lately that they suck?

------------------------------------------------------------------------------------
Lastly, running issues. These really get to me, I feel like I could strangle whoever the people are who made this game.
------------------------------------------------------------------------------------

*When running and wanting to go for another run, sometimes the batsman don't even respond! They say "YES!" but they just stand there! The worst is when they decide to take the run after the fielder throws the ball. It is so frustrating!

*When cancelling a run seeing they won't be able to make it, the batsman decide to run half way down the pitch and then turn around and go back. That is so stupid! if you say "NO!" do you turn for the second run, run and then turn around!? NO! That is the BUG of the YEAR!!!

*Lastly, when running and getting a close run out, after the third umpire has gone through the replay and your batsman is safe, you get NO runs. Nothing! Nothing at all! it's like you just did'nt run. All that hard running for nothing!
------------------------------------------------------------------------------------

I wish I could see these things fixed up and mainly the issue where when an Innings is over, new team members suddenly appear to replace ones you have chosen before hand. This is all too much...The game is actually pretty fun to play, but these bugs are way too many and too frustrating.
 
the run out issues are well known lanokota. for the issue of you r batsmen not taking second runs when running between the wickets, try to make the call when one of your players is fairly close (but not over) the return crease. you will find they fail to respond a lot less then...

the slips one sounds hilarious... sounds a bit like the zab judah chicken dance :D
 
another bug I noticed today, I dunno if its already listed, the bowler sometimes deliver 7 balls an over. This usually happens when you load the save game file
 
Originally posted by Rangeela
another bug I noticed today, I dunno if its already listed, the bowler sometimes deliver 7 balls an over. This usually happens when you load the save game file

I have noticed this also rangeela
 

Users who are viewing this thread

Top