Things the AI should do - suggestions

[legend_master]

Hi all,

thought it would be a good idea to open this thread - possibly duplicating some stuff from the main suggestions thread but thought it deserved it's own.

Basically i wanted to get people's opinion on what would make a great AI for the game. Suggest stuff even if it sounds ridiculous or impossible to put in.

For example, AI should be able to react to the match situation, be able to make good decisions declaring etc

LM

 

[cnbd_novice]

AI should be able to react to the match situation

Well, doesn't that summarize everything??
It should be able to change the batting or bowling lineup (AI) based on the match situation.

 

[aditya123]

The AI must bat according to the following parameters :
1.) required run rate
2.) current run rate
3.) wickets in hand

Wickets in hand should be the most important deciding factor as to what RR the AI will bat.
The next factor under consideration should be the req RR.

The player attributes should decide the manner in which a player will bat.

The AI must set fields according to the match situations unlike EA where the field remain attacking till the batsman scores about 75.

 

[HarryPotter Kid]

if pakistan need 50 off 5 overs and a wicket falls, even if afridi is not next they should bring hime out.

 

[Deleted member 9102]

Edit: Chris Gayle

 

[DiscoStu76]

For general team tactics it is quite important for the teams to know the relative game situation. Take soccer for instance, a team up by 2 goal will play defensively and the other team attackingly.

Cricket is a bit harder to judge this. You know like when your girl walks in while your watching a game and asks "whos winning?" and you look at her angrily and say "its cricket! no ones in the lead!"

It is obvious a game like BLC07 has no idea what fields to set relative to the game situation. So a suggestion for the AI to decide this would be to use the duckworth lewis system after every over to determine teams tactics. IMO the duckworth lewis system is pretty accurate and if the calculations are to be included in the game anyway it would be so simple to use this behind the scenes.

Just an idea for a simple way to judge game situation. Probably a lot easier than trying to write your own algorithm!

 

[Deleted member 9102]

Edit: Chris Gayle

 

[RabbleRouser]

Team Selection should relate to the pitch. For example if it's a turning pitch they should favour playing an extra spinner. Also, the situation in the series and the opposition should influence this. If a team is 2-0 up with one to play they are more likely to rest a star player the same goes for if they are playing Bangladesh/Zimbabwe.

 

[Will_NA]

First of all, great thread LM, showing you're listening to ideas.

1) Leave the ball wide of off-stump unless they are tail-enders
2) Celebrate realistically when they get a wicket instead of just thrusting both arms in the hair and jogging down the pitch
3) Try something out of the ordinary once in a while
4) Have spells bowling round the wicket
5) Look to rotate strike
6) Try and attack lesser bowlers
7) Throw the ball up when they take a catch
8) Drop out of form players
9) Take expensive bowlers out of the attack
10) Play in accordance to the situation e.g. if they require run-rate of 6+, try and hit a boundary in each over

 

[treva]

1 - Play strokes on length if a flat pitch
2 - Play strokes according to the delivery in Test Matches (e.g If a good ball, play it with respect)
3 - Play Agressively according to your line up (e.g In an ODI game if u had two big hitters opening they would play agressively for the first 15 overs)
4 - Change bowlers for the situation of the innings (e.g If needing to break a partnership, bring on a wicket taker)
5 - In a tour/series/tournament, change the line-up according to form
6 - Have different fields according to the batsman (e.g A silly mid off for Hayden)

 

[holmie]

this is more of a stroke sudgestion but i think batsmen that are attacking like afridi, dhoni, boucher, gilchrist etc. should have strokes that are played fast. like inzamam will play easy strokes that dont require quick movement but once he is in an attacking mood then he should speed it up a bit. is that a good idea or does it not seem real?

and also for your career mode, i think your skills should be gained by how much you play of a stroke. like if you keep playing off-drives then your skill in that should improve rather then you playing a game and at the end of the game you get points which you can spend on anything. cuz in real life, you dont practice playing front foot drives in the nets and end up improving your skills at pull shots.

 

[Allrounder18]

If team is AUSTRAILIA than its AI should be coded in such a that ,if u dont use your mind to guess or calculate the next AI tactics you should not be able to win that match by your skills of batting or bowling.

 

[khan31]

Have higher chances for mistakes depending on which team/player. IE Australia shouldn't make many mistakes in the field and people like clarke and symonds should hit the stumps from the inner ring 7/10 times. Other teams such as pakistan will misfield more regularly (2/10 balls that are times well) and not hit the stumps as many times. Also when batting as mentioned before the AI if batting first should pace their innings well. If you bowl well enough and keep their rate say below 5 then after a few overs one of the attacking batsmen should go for a few big shots etc. When batting second they should keep with the rate and hit out if they fall behind ONLY if they have wickets. Little things like that make a big difference.

 

[Jdz]

Make it possible to run out the AI.

 

[fisch]

I'd like to take wickets against the AI and feel like I've earned it.........by deceiving the AI batsman by working them out in one over........for example, setting a batsman up with few outswingers and getting them out with an inswinger.