Test Cricket tweak

Originally posted by mani_gamer@Jun 19 2003, 04:00 PM
ravi for god sakes improve this

Patch makers don't usually respond too well to orders mani_gamer. (I certainly wouldn't)

Please state your requests in a more civilised fashion

Thanks
 
Originally posted by amber22@Jun 19 2003, 03:55 PM
Jonah , use both the files which Ravi sent in my name
Right, I'm using the ones which I received about an hour and fifteen minutes ago with this e-mail...

'Amber, Use this one till advised. Others who already are using the last sent need not bother as I have all of you in my distribution list you are getting it as well.'


I'll now stick with these for a few days to get a better impression of how they perform.


I agree Zim...it may just be your manner, Mani, but Ravi has put an untold amount of hard work and dedication into trying to make a patch we can all enjoy. The least he deserves is a bit of courtesy.
 
im not accussing him :o
he has done a great work B)
and jonah he only told us to post how the patch goes
and what improvements can b made :argue:
 
Ok mani, don't want to start a row, just thought a 'please' wouldn't go amiss...
 
I suppose it has got a bit too confusing for now as to which one to use. Mani the results you saw were of one of the patch where we tried to induce confusion in CPU batsman by introducing CPU difficulty. But as I said before this was simply not tested at all and voila the results are simply very awry. Also with the batting am not sure which ones you are using but the one I am using seems to be by far the best one. I sent you all a last set of files yesterday in which there was a batting and bowling setup files.

Mani if you have got the mail which contained the following text, use the ones that came attached with it :

"Amber, Use this one till advised. Others who already are using the last sent need not bother as I have all of you in my distribution list you are getting it as well."

Hopeully, its all nice and clear now or is it still clear as mud?
 
I played IND VS NZ(cpu) on a normal pitch.NZ won by 2 wkts.I batted first.The batting files looked perfect.I scored 227 all out in 48.1 over or something like that.There were sufficient edges.Tendulkar was run out.Then Sehwag got an outside edge and was caught at slip.Then after a good patnership Ganguly got an inside edge and was caught by the wk.The bowlers bowled beautifully with regular outgoing and incoming deleieviers.Cairns bowled a beatiful incoming ball to Dravid which knocked his off stump off.After 40 runs or so , Kaif was outside edged to wk.Yuvraj played very well with 69 and was the last batsman to be out.
So for batting files I think they are perfect.Edges etc all are perfect.(And I dont know why Mani cant play the sweep shot because I am able to play it comfortably.The reason is he is playing against fast bowelers and that too not on a yorker.The bowl is likely to be missed by the batsman.And mani ;) :up:
dont panic away, Ravi is not in a hurry to release the patch.We will sort every probelm.

Now comes CPU batting.Zaheer was the best bowler early as he got 2 wicket in his 1st 2 overs.Stephen Fleming got an edge to the wk.All the caught shown in the screcard is either by the wk or slip.SO a sufficient amount of edges.NZ lost 3 wickets for 33.But a useful patnership for the 3 rd wk continued.But CPU lost 6 wkts inside the 100 runs.Then as you can see Vettori and Adams were the ones who got the win.
My views is the only thing which needs to be looked in the bowling files is that CPU does not lose 5-6 wkts inside 100 runs at least on a normal pitch.And the CPU goes for boundaries all the time instead of looking to play singles or doubles when the target is not much and specially when they have lost many wkts for a few runs.

The edges for both batting and bowling files are sufficient and according to me need no changes.the batting files are perfect.
Ravi , lets wait for the feedback by Jonah
 
Here are the batting stats.And yes I forgot to tell you that both the LBW's are on a slow ball which bounced off to a considerable heights and struck at the pads.
So the variation in pace also helps sometimes :up:
 
I played another game with WI(cpu) on a green pitch.Wi are 98/5 after 14 overs.This means that they though they always manage the r.rate above 6 but loose too many wickets(although this was a green pitch).2 of them were out of edges which was fine but Lara just throwed his wicket away.He managed just 5 runs before he tried to hit the ball in the air straight and was caught.

So I think that being too much agressive they lose wickets.So what can be done Ravi is they do not play the ball in the air always but look to find the gap and should look to make singles in the middle part of the innings.

Also as I was playing on a green pitch , there was less movement from fast bowlers as was expected from them
So I think you can work on the bowling.exe file Ravi.And Let the edges be as they are(I think so)
 
First off, thanks for the one who pinned this topic at top it really helps. Also thanks a heaps Amber, for you feedback much appreciated.

Getting back to the CPU batting (I will not write much about the Human batting as it is quite good, I have also noticed), I would wish bring to the notice of all the testers :

1. CPU is designed to bat aggressively if the batsman is of aggressive type so no surprise Cairns, Adams look to score fast runs.

2. The lbws, runouts and bowled are very much a necessity in the game hence we cannot forgo those dismissals. Although we can make the top order a lot stronger as you have suggested. I will make those changes right away.

3. The reason you might at times see CPU bats quite aggressively is because it was felt it had to force the Human to change the field settings to stem the run flow. You have to be creative in your field settings, get the right fielders at the right place and you will see you can cut down the run flow. Something like have Lou Vincent in point, Cairns in deep fine leg, Fleming in slips. If you attack a bit too much you have to expect to give away a lot of runs although you can take few wickets. I will ensure there will be less LBWs and Runouts in the update of this patch.

Amber, did you bowl quite a lot of yorkers at all? Also did you always have an attacking field i.e did you not spread the field post 15 overs?

4. It was also felt there should be a wicket fall when the ball is new or during the first 5-10 overs. We wanted to keep the bowling part a bit interesting by forcing the field changes, change in line and length et al.

5. If all of you guys reckon the CPU should preserve wickets in the initial stages of the game so be it, will get those changes done in my update although will not be looking forward to till the weekend. Further testing although with the current patch is still needed I think.

6. I will also get the CPU to bat less aggressively in the middle overs it might really help.

Mani, there is absolutely no need to panic mate some shortcomings are expected at times while the changes are being made as we are not developing a new game but are altering what is already there without have much confirmed input on the files. Also we are not to mind the time it will take to get the perfect one although it will probably not be able to satisfy each and every one. A good compromise is to be made as far as the patch can make the game realistic and long lasting. We have to bear in mind this patch is being done for 50 overs ODI and for those who seek a realistic game and not a quick 20 over game. Keeping in mind these we shall continue to test it a bit more and hopefully with the cooperation of all you guys we can have a good one shortly.
 
Well Ravi , i dont have the habit of bowling too many yorkers.I just bowl 1 yorker per 2 overs.And also I am not dissappointed with the way the CPU bats.It;s only it should preserve some wickets and good to hear it will be there in the next update.
And dont change that LBW thing.Those LBW were not on yorkers but on slow balls bouncing on the grounds.So I think it should be retained.

Thanks
 
Furher to this (and just a quick note Ravi for reasons I explained to you yesterday :( ), I agree that the cpu appears to lose too many early wickets. 1, 2 or maybe 3 down after the first 15/20 would be great (although obviously this should vary to keep the game interesting).
Also, Ravi, as you and amber suggested, it would be great if the cpu was less aggressive from overs 15 - 40, looking for more 1's and 2's, and the occassional big hit and boundary. Aggressiveness should ideally then pick up gradually to the final few overs (say 46 onwards ?) of hard hitting (although not every ball ;) !). Hopefully this will preserve more wickets and allow the cpu to keep a realistic run rate.
I'm not sure if this is possible (although if it is I know you'll be able to do it Ravi!), and it'll be interesting to see how the cpu chases a target if the above is implemented (maybe more close finishes?).
What do you guys think?

Unfortunately I doubt if I'll be able to post any further feedback till tomorrow at the earliest :( .
Cheers :) .
 
Originally posted by crick4life@Jun 19 2003, 12:39 PM
I suppose it has got a bit too confusing for now as to which one to use. Mani the results you saw were of one of the patch where we tried to induce confusion in CPU batsman by introducing CPU difficulty. But as I said before this was simply not tested at all and voila the results are simply very awry. Also with the batting am not sure which ones you are using but the one I am using seems to be by far the best one. I sent you all a last set of files yesterday in which there was a batting and bowling setup files.

Mani if you have got the mail which contained the following text, use the ones that came attached with it :

"Amber, Use this one till advised. Others who already are using the last sent need not bother as I have all of you in my distribution list you are getting it as well."

Hopeully, its all nice and clear now or is it still clear as mud?
yes ravi im using that file only
its good
but atleast fix my sweep shot as i love t play that on spinners
plzzzzzzzz :huh:
 
Originally posted by jonah@Jun 20 2003, 09:18 AM
Furher to this (and just a quick note Ravi for reasons I explained to you yesterday :( ), I agree that the cpu appears to lose too many early wickets. 1, 2 or maybe 3 down after the first 15/20 would be great (although obviously this should vary to keep the game interesting).
Also, Ravi, as you and amber suggested, it would be great if the cpu was less aggressive from overs 15 - 40, looking for more 1's and 2's, and the occassional big hit and boundary. Aggressiveness should ideally then pick up gradually to the final few overs (say 46 onwards ?) of hard hitting (although not every ball ;) !). Hopefully this will preserve more wickets and allow the cpu to keep a realistic run rate.
I'm not sure if this is possible (although if it is I know you'll be able to do it Ravi!), and it'll be interesting to see how the cpu chases a target if the above is implemented (maybe more close finishes?).
What do you guys think?

Unfortunately I doubt if I'll be able to post any further feedback till tomorrow at the earliest :( .
Cheers :) .
No worries there Jonah, these can be done and I already have implemented it in the patch. By the time you are back I assure you will get the updates with those pointed out by you guys implemented. I am trying the patch out right now and it is looking really good, the CPU is still scoring at good rate but is more defensive, less shots in the air. This probably needs another game or two from me to be doubly sure, will advise you guys probably in another 2-3 hours if the patch is shaping up well. Take care Jonah and make sure you get a lazy boy(I mean the chair) to play the game it will help your back.

Do I take we are all happy with the batting setup apart from Mani who wises to make the sweep shot a lot easier to play. Mani, if it is your personal preference to play that shot frequently then I suggest I can send just that one which you can use after having installed the patch.
 

Users who are viewing this thread

Top